CM Wiki, CM Google+, Fireball Wiki, Fireball Google+
Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2
Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems
Introduction
This is CyanogenMod 10.2 (cm-10.2) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.3. Usage of this ROM indicates that you understand...
the warranty on your device is void;
the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).
Preparations and Installation
Get your phone ready for a new ROM
You must have an unlocked bootloader or be S-OFF (read here for instructions)
Before leaving your stock based ROM:
Turn on all GPS location services: Settings > Location > (all three location services) = On
Change network mode to CDMA/LTE: Settings > Mobile Data > Preferred Network
Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
Install a custom recovery: CWM or TWRP
Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
Perform the factory reset function in recovery and additionally wipe the /system partition
Flash the CyanogenMod zip (do not flash gapps yet)
a) If you are S-OFF, you can reboot now.
b) If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands one at a time:
Code:
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
The first time CM boots, change the following network settings and then reboot:
Select LTE/CDMA/EvDo network mode: Settings > (Under Wireless & Networks) More... > Mobile networks > Preferred Network
Select RUIM/SIM subscription: Settings > (Under Wireless & Networks) More... > Mobile networks > CDMA subscription
(Optional) Reboot to recovery and flash the GApps version corresponding to CM 10.2.x
Note: many apps require Gapps to be installed before GPS will lock-on a location
Updating to a new build
Make a backup of your current build in recovery
Install the new build
If you are S-OFF, reboot
If you are S-ON and HTCDev Unlocked, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.
Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.
Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
There is currently a nasty little acpuclk bug that can cause boot-loops after rebooting the phone. A battery pull remedies this.
Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.
Most recent builds: goo.im
Archive/Mirror: mediafire.com
goo.im folder structure: visit the page to read release-specific notes
mdm-releases - Based on CM 10.1.2 stable using linux kernel 3.0
kernels - Enhanced kernels for use only in CM
cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases
GApps
Download the GApps version corresponding to CM 10.2.x
Reporting Issues and Getting Help
Policy on bug reports:
You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
logcat or GTFO
If these steps are not taken, your report will be ignored.
How to gather helpful data for troubleshooting
How to use the issue tracker
Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.
Change Log
CyanogenMod BBQLog
CyanogenMod CMXLog
fireball-specific changes:
20131107 - SMS messages no longer split at 160 characters
20131106 - fade-out animations fixed
20131029 - substantial radio updates, increase speakerphone mic volume, new power managment code in kernel
20131020 - speakerphone and headphone volumes adjusted
20131018 - usb tethering fixed, speakerphone mic fix, wake-on-volume fixed
20131015 - flickering panel fix
20130909 - initial(ish) release
Click to expand...
Click to collapse
Known Issues
Official Builds
Display flickers when brightness is set at max Workaround in post 3
Device boot-loops after restarting Workaround in post 3
High pitch background noise in camcorder recordings (only seems to affect some users)
Auto-brightness is slow to adjust after display-on
Many apps require Gapps to be installed before GPS will lock-on a location
Known Issues that will not be fixed
OTG mounting of USB sticks - Likely no hardware support
FM Radio - Likely no hardware support
MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
Workaround in post 3
Development Information
The following trees are needed to build CyanogenMod 10.2
CyanogenMod/android_device_htc_fireball
CyanogenMod/android_device_htc_s4-common
CyanogenMod/android_device_htc_msm8960-common
CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.2 build to pull necessary proprietary files into vendor/htc.
Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
htc-msm8960-devs: a talented group of developers with lots of patience while I was learning
utkanos, KemoNine, and Jin^eLD for general building questions
jose51197, Linch89, and blazingwolf for early testing reports
squeezyb for selling his fireball at a discount so I can share it with other developers
Restoring a borked radio
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
FAQ and Workarounds
The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!
Stuck at the HTC boot screen
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times
Boot-loops
There is a known bug in acpuclk which affects all of the htc msm8960 devices. When you reboot your phone, it might crash at the CM logo and start boot-looping. This is the kernel panicking when it continuously fails to bring up cpu1. The workaround is a simple battery pull. It's pretty reliable. After CM loads, this bug doesn't affect the device.
Screen flicker
If you notice the screen flickering rapidly:
1) Make sure you're running build 20131015 or newer
2) Try lowering the brightness a bit or using auto-brightness - this usually only occurs when the brightness is set very high
3) If using auto-brightness, when you turn on the display, let the brightness settle before touching the screen
"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).
"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks:
Network mode = LTE/CDMA/EvDo
CDMA subscription = RUIM/SIM
Usage of this ROM on non-Verizon carriers is unsupported. That doesn't mean it won't work; it just means you won't get support from me to try and make it work. There are several users that use this phone either out of the country on GSM networks, or on prepaid carriers in the US. I just ask that discussion specific to these scenarios be kept in separate threads -- perhaps @jose51197 can start a thread and I'll link to it from here.
Missing menu button in applications
First, set this: Settings > Buttons > Allow custom buttons = True
Option 1: Re-associate the recent apps button: Settings > Buttons > Recents Button > Short press action = Open/close menu
Option 2: Use action overflow: Settings > Buttons > Menu button > Show action overflow = True
Text messages from 6250 with message VZWNM: #
See this thread and this post.
ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.
Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/
ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.
Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.
MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP
Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install gvfs
Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.
GPS doesn't acquire a signal
From recovery, make a nandroid backup of CM
Wipe data, cache, and system
Restore a stock-based ROM backup
Enable all location services: Settings > Location > (all three location services) = On
Use a GPS application to get a lock on your position (I use GPS Test)
From recovery, wipe data, cache, and system
Restore CM backup
Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
Restart the phone to recovery and connect the USB cable to a Windows computer
In recovery, use the mount USB feature:
ClockworkMod(-based): mounts and storage > mount USB storage
TWRP: Mount > Mount USB Storage
When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
Your /sdcard partition should now be accessible
Encryption
Pre-requisites: TWRP 2.6.0.0 or newer
Encryption procedure:
Make a full backup in TWRP
Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
Reboot and let phone battery charge to 100%
Turn on Airplane mode
Settings > Security > Encrypt phone
Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
Wipe your data partition
Restore your backup
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
mdmower said:
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
Click to expand...
Click to collapse
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Edit. As far as things needing fixed, lol I honestly can't find anything major. Don't have screen flicker. Focus works on cam and video. Avrcp function works great and sends metadata to cars radio screen and the sound quality over Bluetooth is better than 10.1. Only thing that is minor is my headset button doesn't work with 10.2.
Sent from my Incredible 4G LTE using Tapatalk 2
spectre559 said:
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Click to expand...
Click to collapse
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
MJL99 said:
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Click to expand...
Click to collapse
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
mdmower said:
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
Click to expand...
Click to collapse
How about the 9/8 official nightly? The file size is definitely smaller than the experimental build I noticed but newer. Also how are these builds comparable to what you have posted on goo? I see there's a 9/9 build but the file size is bigger than the most recent one on get.cm.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
How about the 9/8 official nightly?
Click to expand...
Click to collapse
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
mdmower said:
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
Click to expand...
Click to collapse
Doh! Took me a minute. Lol
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
Click to expand...
Click to collapse
You are right. Apparently that number corresponds to the maximum value of a 32-bit signed integer. http://en.wikipedia.org/wiki/2147483647
Ok, fireball is now on cm-10.2 nightlies.
mdmower said:
Ok, fireball is now on cm-10.2 nightlies.
Click to expand...
Click to collapse
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Sent from my SCH-i705 using Tapatalk 2
jrior001 said:
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Click to expand...
Click to collapse
Oh, no worries there. Other projects were already basing themselves on cm-10.2, I just wanted to get things in better shape before flipping the switch here (well, that and a severe lack of time to get things organized).
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Click to expand...
Click to collapse
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
mdmower said:
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
Click to expand...
Click to collapse
That worked. Initial boot from a flash over previous 10.2 build reverted to nv. Changing it and rebooting saved the settings to ruim/SIM.
Thanks for the heads up about fix permissions too.
Sent from my Incredible 4G LTE using Tapatalk 2
Camcorder feedback
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
mdmower said:
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
Click to expand...
Click to collapse
No high pitched noise on recordings for me on newest official nightly, 9/11. I also do not have the panel flicker.
Sent from my Incredible 4G LTE using Tapatalk 2
Related
Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Help
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
hatoo said:
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Click to expand...
Click to collapse
It's in the works. CM10.1 compiles just fine, but i'm getting bootloops due lack of ion support in 2.6 kernel. I've managed to (mostly) port spro-specific things to CodeAurora's 3.4 kernel and fixed all compilation errors, but spro's device configuration routine is sort of different from vanilla msm8260 (some things are being configured by aboot, yet it's performing some checks that are unclear to me at the moment). Currently kernel fails to boot and device is getting into the blink-camera's flash-and-switch-screen-off mode (same mode device gets when it's turned on with volume-up+volume-down keys).
Oh, and by the way: i've tried to contact both Compal (odm and actual kernel developer for spro) and Dell to get information about what kernel was used in that unreleased 062-world wide dell rom. Compal's mailserver refused to deliver my message, and Dell's opensource departament people responded only once askung if i seek information on 2.6 kernel. I've re-stated that i'm seeking information on 062 rom and 3.x kernel - no word from them since then
So, we're up to ourselves with this one. If anyone's capable and willing to help with resolving 3.4 kernel boot issues - drop a line into this thread - i'll upload my current kernel tree to github.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
Click to expand...
Click to collapse
Power+volume up+home if i recall it correctly. Another way is to issue
Code:
fastboot boot your-recovery-image-name.img
while in fastboot mode.
For those who it may concern
Here's a list of my SPro-related repos (in order of appearance):
2.6 kernel - original dell sources bumped to .14 along with other additions. should be suitable for ics-based roms.
caf-3.4 kernel - my current point of interest.
device/dell/msm8660-common and device/dell/streakpro - device source trees for cyanogenmod 10.1, both based on htc pyramid device trees.
While I've never had a SPro, good luck with it.
Awesome!
I use GS01 as my main device, so I'm looking forward to your custom ROM!
Sort of update.
Dell responded:
I apologize for the delay. I have learned that we did not update to 3.x. I think you may have the latest versions. Thank you for your inquiry.
Click to expand...
Click to collapse
So, we're on our own. Great..
Request
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Is this ok?
kibuuka said:
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Click to expand...
Click to collapse
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
hatoo said:
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
Click to expand...
Click to collapse
Yep just what I needed, thanks hatoo.
kibuuka said:
Yep just what I needed, thanks hatoo.
Click to expand...
Click to collapse
Hi Kibuuka!
What about DS5 ICS development, are still working on it?
Regards...
Dell steak 5 can't enter fastboot and always restarting somebody help me pls
unlock
Not really the right thread to ask that, but not able to get into fastboot or not able to get into recovery?
Dell Streak Pro GS01 (E mobile)
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
shakes1883 said:
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
Click to expand...
Click to collapse
First of all - as a rule of thumb you're better NOT to use one-click solutions for anything - these ARE evil.
Let's think you don't want to/can't disassemble it.
You'll need:#1 drivers for Spro - grab it here, #2 fastboot and adb binaries - grab these, #3 one of the stock ROMs - TheManii did a great job collecting them - select one containing SPro in filename from here, #4 CWM recovery image - grab this one (courtesy of TheManii) and #5 - superuser flasheable package (by TheManii as well)
You have to wait until phone's battery is fully drained.
After that you need to connect it to pc. It will enter so called "charge-only state" (charging battery animation). Wait until it fully charges (LED will become green). Disconnect it from pc/power supply now.
Then you'll need to turn it on by pushing power button AND volume down at the same time to enter fastboot mode - screen will go black with two lines on it:
Code:
FATBOOT!!!!
Version 0.5
Connect your phone to pc - you'll see third line
Code:
USB cable connected
and windows will ask for drivers for device (if you don't have them installed already)
After drivers installation you're set to fix you problem.
Open command prompt and cd to a dir containing adb and fastboot binaries (let's assume full path is y:\adb\ and you have copied CWM image into this folder):
Code:
cd y:\adb\
Then boot (we don't flash it this time preserving your device's warranty ) into CMW recovery
Code:
fastboot boot y:\adb\SPro-6.0.1.2.img
You'll see good'ol CWM recovery screen. Navigate to "Mounts and storage", then select "mount USB storage". Your pc will now be able to access phone's internal and external storage. Now copy ROM image of choice and superuser package to either of phone's partitions you've connected to pc on previous step.
Select Unmount in CWM menu (AFTER you did a safe device removal in windows - thin precaution will save you some nerves).
Navigate to "install zip from sdcard", then to "choose zip from sdcard", select ROM image you've copied previously, select "Yes - Install update-zip-you-have-selected.zip"
CWM will install ROM image for you.
Now do the same selecting superuser package instead of ROM image and install it as well.
Select "reboot system now". If everything's ok you'll see your device booting into your newly installed ROM. If it doesn't - get to fastboot mode again, boot CMW image and do a factory reset using it ("wipe data/factory reset").
I'll just leave it here
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
kibuuka said:
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
WOW! AMAZING! Never expect Streak pro will have CM. Thank you so much for you work.
Finally!!
So nice ROM!!
I love you Kibu lol
Please Support Custom rom dell streak pro
I know many xda dev community is a good: Good:, the dell streak pro help you make a rom version 4.x so it works better : O
thanks!
- CPU: Qualcomm MSM8260A Snapdragon, 1.5 GHz Dual-Core Processor
- RAM: 1 GB Memory: 4 GB
- External Memory MicroSD (T-Flash) up to 32 GB
- Camera: 8.0 MP, support LED flash, autofocus
- Cinematography: FullHD 1080p @ 30fps
- Battery capacity: 1520 mAh
- Super AMOLED Plus display with 16 million colors Resolution giai540 x 960 pixels Size 4.3 inches
- OS: 2.3.5 Androi
are looking forward to the help of kibuuka well as helping people in xda
kibuuka said:
Not creating separate thread for this, just teasing a bit .
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
hope you help fix bugs present in nodules rom, dell community treak pro users have been waiting for this day ever. thank you very much
GEEWIZ 3.4 SCH-I500 JZO54K JELLY BEAN 4.1.2 ROM/KERNEL
RETIRED -- GEEWIZ 3.4 WAS THE FINAL RELEASE OF GEEWIZ BASED ON ANDROID 4.1
OTHER AVAILABLE GEEWIZ VERSIONS:
GeeWiz 4 - AOSP Jelly Bean 4.2: http://forum.xda-developers.com/showthread.php?t=2088224
GeeWiz 3.4 is a ROM for the Samsung Fascinate, based on AOSP Jelly Bean 4.1. Like it's predecessors of the same name, GeeWiz doesn't aim to provide a lot of bells and whistles or incorporate all of the latest and greatest tweaks and enhancements developed by the community; the aim is to provide a basic, stable, functional device.
GeeWiz 3.4 uses a modified version of the GeeWiz 2.8 Gingerbread (Linux 2.6) kernel with a number of very specific tweaks/hacks in order to continue to support the proprietary Samsung RFS file system and other features I wanted to carry over. As a result, this ROM may not be used in conjunction with any other Kernel, and this Kernel cannot be used in conjunction with any other ROM. Please consider it a "matched set", and they will always be updated/distributed together. XDA community developed enhancements to the ROM or Kernel are encouraged, and will be given prominent feature status in this post.
Your device needs to be set up as stock or stock-like (e.g. GeeWiz 2.8) before installing this ROM/Kernel. If you are currently running with an MTD-based platform, the device must be reverted back to the original OEM volume format. Please refer to the forum/thread were you acquired your current ROM for guidance on how to revert the device as necessary.
Installing this ROM/Kernel or any other provided component(s) will void your device's warranty, and I cannot be held responsible for any damages of any kind (including data loss) that are incurred either directly or indirectly by these packages and components. What you do to your device is ultimately your problem!
FEATURES
Android Jelly Bean AOSP build JZO54K (android-4.1.2_r1)
Google Apps version JZO54K from the Galaxy Nexus
All devices (GPS, compass, orientation, camera, flash) are functional
Wifi (WPA/WPA2) and Bluetooth Tethering support
Supports OEM DBDATA volume to keep performance reasonable
Supports both RFS and EXT4 formatting on all volumes
OEM USB modes (CD-ROM/Kies/MTP) replaced with standard Android Mass Storage
Advanced Battery Settings: Maximum Charge, Automatic Recharge Point
Advanced CPU Settings: Maximum/Minimum Clock Speed, Governor Selection
Advanced In-Call Volume Boost Selection
Backlight Notifications built into system, controlled by the OS
Supercurio Voodoo Sound 10
Fascinate Dock audio simulates a true USB audio device for seamless output path switching
Custom Dock options - Enable BLN, Stay Awake, Enable audio output
CREDITS
While it would be impossible to remember/cite every possible reference that was used during development, I would like to specifically thank the following teams/individuals for making their work public so that others could learn from it and in more cases than not, shamelessly "borrow" it:
jt1134 - A primary source of knowledge for all things Samsung Fascinate
sgtkwol - Maintains a Linux 2.6 kernel for the Epic that provided a vast amount of reference material for the kernel updates
pawitp - Fixed my video driver changes to eliminate a 'microlag' issue (thank you!)
Entropy512- Customizations to allow WPA/WPA2 Wifi Tethering to work on the Galaxy S
teamhacksung - Maintains a large repository for all Galaxy S devices, I can't count how many code compares I did against their material
Cyanogenmod - The fact that this ROM can make a call at all is thanks to this team. So much of this effort is based on theirs!
rxwookie - A long-time supporter of all things GeeWiz and always takes the time to help other folks out here. I think he probably knows more about GeeWiz than I do!
ACTIVATION AND PROVISIONING
While I have no reason to believe that activation/provisioning wouldn't work properly on this ROM, it is a difficult thing to test on CDMA networks. Until it's been established that activation/provisioning is indeed working properly, I suggest you do not use anything like the ODIN "EFS Clear" option that may affect it. If the phone was properly provisioned before installing this ROM, it should maintain that provisioning. I have successfully activated a Fascinate on this ROM, but have not tested the process enough to be fully confident with it.
KNOWN ISSUES
USB Mass Storage / ADB may not work after device has been docked
After docking and removing the device from a Samsung Fascinate dock, USB Mass Storage and/or ADB may stop working. When this occurs, the only way to restore USB connectivity is to power off the device and power it back on. Rebooting is not sufficient and will not alleviate the problem.
FIRST-TIME INSTALLATION RECOMMENDATION
This ROM performs significantly better when the device uses the EXT4 file system. Unfortunately, using ODIN will always format the device with the RFS file system. Unlike previous versions of GeeWiz, the new "Full Wipe" ODIN package has been modified such that it will format the data volumes (DATA, DBDATA, CACHE) with the EXT4 file system on the first boot. This is now the recommended installation method for first-time installation.
If the "Full Wipe" ODIN package is not used, please note that your data must be wiped manually if coming from another ROM to avoid problems, and I strongly recommend converting, at minimum, the data volumes of the device (DATA, DBDATA, CACHE) to the EXT4 file system.
UPGRADING FROM GEEWIZ 3.2/3.3
GeeWiz 3.2.x/3.3.x Versions can be upgraded directly to GeeWiz 3.4 without a need to wipe the device data or revert the file system back to RFS. The EDIFY update-zip below is compatible with most, if not all, recoveries and will work regardless of if the device is formatted with RFS or EXT4.
Your Dalvik-cache will be automatically wiped, so the first reboot will take a long time
Due to problems with some Google services after a kernel change, the Google Services Framework package will have its data cleared during installation. You will be prompted to accept Google's location services again
DOWNLOADS
EDIFY Update-Zip (ClockworkMod / GeeWiz Recovery) Compatible Downloads
GeeWiz 3.4 ROM/Kernel (EDIFY Update-Zip)
http://www.mediafire.com/file/ascgikdaqdg3ai5/geewiz-3.4-syskernel-01122013.zip
MD5: 6b2e280f9d51492febec43b8b9fa3bd4
GeeWiz 2.8 Recovery (EDIFY Update-Zip)
http://www.mediafire.com/file/5fxee76vrxv28eq/geewiz-2.8-recovery-04162012.zip
MD5: 9869d3138279d99f1237a442f7573cad
ODIN Compatible Downloads
GeeWiz 3.4 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
http://www.mediafire.com/file/2266vgo7uma5xmk/geewiz-3.4-fullwipe-01122013.tar.md5
MD5: 0d6c2cf955d0024c925c2d10ce046e1d
GeeWiz 3.4 ROM/Kernel (ODIN)
http://www.mediafire.com/file/jzfwybqu6ns70ay/geewiz-3.4-syskernel-01122013.tar.md5
MD5: 46e17141a8f8a8ae48001c3e4653e088
GeeWiz 2.8 Recovery (ODIN)
http://www.mediafire.com/file/h5gov2c1r8836tj/geewiz-2.8-recovery-04162012.tar.md5
MD5: b70d4063dffaa9cd89629f307d3beae5
SOURCE CODEThe entire baseline for GeeWiz is available on github: https://www.github.com/djp952.
Device repo: android-platform-device-samsung-atlas3g (branch android-4.1.2_r1)
Kernel repo: android-kernel-atlas (branch android-4.1.2_r1)
Please see post #2 of this thread for an overview of how to build the GeeWiz ROM/Kernel from source as well as how to package your modifications. I would be happy to include any XDA community developed modifications or enhancements to the baseline as featured packages, add-ons or patches for GeeWiz!
Disclaimer: djp952 reserves the right to mercilessly kang your changes and assimilate them when you fix things that he was unable to. djp952 will also give you *major* props and full credit for the fix, so it's not that bad, right?
HOW TO BUILD THE GEEWIZ 3 ROM AND KERNEL
A common request I've gotten is how to build either the GeeWiz ROM or kernel from source. I think GeeWiz 3 is a little less intimidating as a first step for getting into AOSP builds since it doesn't stray too far from the Android baseline, and the kernel is based on Samsung's stock model for the device rather than the enhanced MTD model. Whatever the reason, I'm happy to try and describe how I build these components and generate the packages that I post for the community. Sometimes it's normal, sometimes it's a bit wonky, but as long as I don't miss anything important it should be a workable process for anyone that would like to get into building custom Android builds.
I think GeeWiz 3 would be a great learning tool, it works as-is but leaves enough room for additional customizations and enhancements that it may be a better place to start than jumping into something like Cyanogenmod or AOKP as your first project. It's up to date at the moment with the latest Android code as well, so that's a definite bonus as opposed to working with something like Gingerbread where tricks you learn may not apply to the next project you take on.
BUILD ENVIRONMENT
I use Ubuntu 12.04 Desktop x64 for my Android build environment, and even though Google states that this environment is "Experimental", I've not run into any issues with it. To get started, simply follow the directions Google has provided here:
http://source.android.com/source/initializing.html
If you are running on Windows x64, I can also recommend using a Virtual Machine as your build environment. I like Oracle VirtualBox the best, but the stock Fascinate code by Samsung has major USB problems with it, you won't be able to use ADB or Heimdall. For Fascinate-specific development I recommend VMWare Player since it can work with the stock USB. Note that you need an x64 OS and a CPU with Virtualization Support to host an x64 guest OS regardless of the software you choose. The best performance and compatibility will come from installing Linux natively on your system.
DOWNLOAD GEEWIZ SOURCE TREE
Once your environment is set up, you of course need some source code. I've opted to use Google's repo tool and AOSP manifests to control the source tree, so the first thing you need is the Google repo tool. Follow the first section of this document, entitled "Installing Repo":
http://source.android.com/source/downloading.html
I have two separate "builds", or in Android terms Manifests out there. One is called DEFAULT and includes just changes to AOSP necessary to support the Fascinate. The other is called CUSTOMBUILD and adds the light OS customizations I have done. Since I never use DEFAULT and I'm not sure t even builds at the moment, we're going to use CUSTOMBUILD, or as it's called here at XDA "GeeWiz".
Open a terminal window to your home directory (~/)
mkdir android
mkdir android/platform
cd android/platform
repo init -u https://github.com/djp952/android -m custombuild.xml -b android-4.1.2_r1
What we just did was initialize the repository for AOSP, but haven't downloaded anything yet. The -u argument to repo tells it where to find the manifest XML files. In this case, my github "android" repo. The -m tells it what manifest to use. The -b tells it what branch to pull. This is important because like most folks, I have multiple branches out there. I have been indicating at the very end of the first post what the current active branch is, android-4.1.2_r1 right now.
At this point, I suggest going into the ~/android/platform/.repo/manifests directory and having a look at the manifest file. (.repo is a hidden folder). Open up custombuild.xml in GEDIT and you can see that I've taken the AOSP manifest and simply replaced portions of it to point into my own github repos for things I've changed. I'll try to include details on how I manage this below so you could do something similar if you want to.
The most time-consuming part of building Android is downloading the code. Can't go much farther without it, so get yourself a cup of coffee and a good book ...
In the terminal, at the ~/android/platform directory
repo sync
The SYNC command uses the manifest to go get all the code. Most of it is going to come from Google, but all the bits I've altered will come from my github instead. It's going to take a very long time to download.
BUILD GEEWIZ ROM
Once downloaded, we have to choose what device to build for. GeeWiz has two target devices, "atlas" and "atlas3g" (Technically, there are three as I use the same build for "toro" - VZW Galaxy Nexus). Atlas is the Wifi-only target known here as "GeeWiz Media". Atlas3G adds to that changes required to include voice/data support (mostly courtesy of Cyanogenmod!). Let's assume if you're reading this, you're interested in Atlas3G.
In the terminal, at the ~/android/platform directory
source build/envsetup.sh
lunch
The "Lunch Menu" (haha Google) will present you with a list of device builds to choose from. You can select by number, or you can type in anything not on the menu. As of this writing, the build we want is #8, full_atlas3g-userdebug. userdebug generates a generally release-quality build, but doesn't odex (pre-optimize) the APKs and has some additional debugging support you wouldn't ordinarily find. You could also type in full_atlas3g-eng for an "Engineering" build or full_atlas3g-user for a "Release" build. I think you'll prefer userdebug most of the time.
Select 8 - full_atlas3g-userdebug
make -j4 rompackage
This will kick off the build. It will take a long time the first time through. The rompackage argument is something I added to AOSP to support the Fascinate. This will build the EDIFY update-zip that I upload for everyone and use to generate the ODIN packages (more on that later). On typical Android devices, you would use otapackage (update-zip install) or updatepackage (fastboot install) instead. Fascinate is a special needs child, so it gets a special needs build process.
Once it's done, provided I didn't forget anything important here, you'll have a full ROM/Kernel package ready to be flashed via Clockworkmod or GeeWiz Recovery in the ~/android/platform/out/target/product/atlas3g folder. It will be named along the lines of full_atlas3g-rom-YYYYMMDD.HHMMSS.zip. Making a package for ODIN involves more steps, but I'll get to that. First I have to tell you how to build a modified Kernel ...
BUILDING THE GEEWIZ KERNEL
The Atlas and Atlas3G repos have a pre-compiled kernel in them that is packaged with the ROM build. This section will describe how to build and include customized versions of that kernel. First step is, of course, to get the source code. Both ROMs share a kernel but due to differences in the ramdisk (initramfs), they are built independently.
In a Terminal, at the ~/android directory
git clone https://github.com/djp952/android-kernel-atlas.git
cd android-kernel-atlas
git branch android-4.1.2_r1 remotes/origin/android-4.1.2_r1
git checkout android-4.1.2_r1
Now the build environment needs to be set up. I use the compiler provided with AOSP to build the kernel as this is how Google does it. If you are using a different compiler, or have put your AOSP tree into a different location, you may have to modify these commands slightly.
In a Terminal, at the ~/android/android-kernel-atlas directory
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=~/android/platform/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
NOTE: From this point forward, don't close that Terminal, otherwise you will have to execute the environment export commands again.
The kernel is built in three steps. This is necessary because the Fascinate doesn't conform to Android's models and we have to include the ramdisk (initramfs) in the kernel image. The first step is to select which device you are building the kernel for, which in this case will be "atlas3g_defconfig". (The other configuration for GeeWiz Media is called "atlas_defconfig").
make atlas3g_defconfig
This initializes the kernel build for Atlas3G. Since we need to build the ramdisk as part of the kernel, the next step is to generate any loadable kernel module (.ko) files that need to be part of that ramdisk
make modules
The way I have the kernel set up, it will pull the necessary files for the ramdisk by looking at the device "initramfs.list" file, in the AOSP tree. The file that describes the atlas3g ramdisk, for example, is in ~/android/platform/device/samsung/atlas3g. If you examine this file you can see that it lists where all the files should come from, relative to the kernel source root directory. This explains why I went through how to build the AOSP tree before the kernel, the kernel depends on the AOSP build. Provided everything is in the right place, it's time to build the kernel
make
This executes the main kernel build. Should any ramdisk files be missing, it will error out early on and let you know what the problem is. Assuming everything goes well, your kernel will be in the ~/android/android-kernel-atlas/arch/arm/boot directory. It's named zImage and it's the combined kernel/ramdisk required for the Fascinate.
This zImage file can now be flashed directly to the device with Heimdall, packaged up for ODIN, etc. However in order to make it part of your AOSP build and corresponding EDIFY update-zip, we have to copy it into the AOSP tree and rebuild the ROM. It's a bit tedious, and other folks have different and more streamlined ways of accomplishing this, but this method has worked for me.
cp ~/android/android-kernel-atlas/arch/arm/boot/zImage ~/android/platform/device/samsung/atlas3g/kernel
cd ~/android/platform
source build/envsetup.sh
lunch full_atlas3g-userdebug
make installclean
make -j4 rompackage
This set of commands will clean out and rebuild your ROM package with the updated kernel.
CREATING ODIN PACKAGES
While not the most popular way for people to install your ROM, no guide would be complete without describing how to generate the ODIN-based installation packages. I like to provide a "Full Wipe" ODIN package that will take care of resetting the device while flashing the new ROM/Kernel, it's an easy way for people that are comfortable with ODIN to just completely replace the contents of their phone with your stuff. For this section, I'm going to assume that you are using GeeWiz Recovery, version 2.8 or later. Other recoveries will work, but as you may expect I'm most familiar with the one I made and I know for certain it has all the necessary features in place.
The ODIN factoryfs.rfs file must be generated by formatting the SYSTEM volume with RFS and then installing your ROM:
Copy your generated EDIFY update-zip to the SDCARD
Reboot into GeeWiz Recovery
Wipe the device data by selecting Wipe Device Data and then Wipe all User Data (Factory Reset)
Press the HOME key to return to the main menu
Format the SYSTEM volume with RFS by selecting Manage Volumes / Format Volumes / Format SYSTEM / Format SYSTEM [rfs]
Press the HOME key to return to the main menu
Select Install Update Package, and choose your EDIFY update-zip to install
After the installation is complete, reboot the phone by selecting Exit from the main menu. Not rebooting the device after the flash will result in a bad ODIN file more often than not. Trust me on this one.
After the device has fully booted, reboot it back into GeeWiz Recovery. The next step will be to generate a backup of the RFS-formatted SYSTEM volume to ultimately use with ODIN. GeeWiz Recovery can create these by choosing to execute a "raw dump" of the volume:
Select Manage Volumes / Backup Volumes / Backup SYSTEM / Backup SYSTEM [raw dump]
GeeWiz Recovery tries to keep volumes unmounted after it's done working, so the SDCARD must be mounted before the contents can be accessed with ADB:
Press the HOME key to return to the main menu
Select Manage Volumes / Mount Volumes / Mount SDCARD
GeeWiz Recovery will store the backup as /sdcard/backup/volume/SYSTEM-YYYYMMDD.img.gz, so as an example, I might pull it to my home folder with this command:
adb pull /sdcard/backup/volume/SYSTEM-20121022.img.gz ~/
The .gz file will contain a compressed copy of the backup, just open it up, extract the file, and then rename it to factoryfs.rfs. This is the SYSTEM volume for ODIN. There are also a number of other files you can include in your ODIN package to perform various other flash or wipe operations (I'll tell you where to get them, too)
boot.bin - Will replace the primary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
cache.rfs - Will wipe the CACHE volume; necessary if you want the device to boot into recovery automatically and run a command
dbdata.rfs - Will wipe the DBDATA volume
factoryfs.rfs - Will replace the SYSTEM volume
modem.bin - Will replace the CDMA modem
movinand.bin - Will wipe the DATA, PREINSTALL and FOTA volumes
param.lfs - Will replace the parameter block. Semi-dangerous to include, but required to ensure an initial boot into recovery mode
recovery.bin - Will replace the RECOVERY kernel and ramdisk
Sbl.bin - Will replace the secondary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
zImage - Will replace the BOOT kernel and ramdisk
To generate an ODIN-compatible tarball, gather the files you want to include and execute the following commands from a Terminal. Replace tarfilename.tar with the name you want to give the tarball, and replace file file file file with the names of the files from the table above you want to include:
tar --format=ustar -cf tarfilename.tar file file file file
md5sum -t tarfilename.tar >> tarfilename.tar
mv tarfilename.tar tarfilename.tar.md5
NOTE: If you rename the .TAR file, it will invalidate the MD5 checksum and you will have to md5sum it again.
OK, where to get the files. You can access a "full stock" ODIN package for the Fascinate, like the EH03 version that is available here on XDA to get copies of all the stock versions of these files. Or, you can use the ones from my ODIN "Full Wipe" package if you'd like as well. My ODIN tarball has a gimmick that you may find useful. If you include my copies of cache.rfs, param.lfs and recovery.bin, the device will initially reboot into recovery and automatically format the CACHE, DATA and DBDATA volumes with the EXT4 file system. It's a relatively simple trick, but an effective one to help improve the performance of your ROM. I also like to provide a "syskernel" tarball that includes only factoryfs.rfs and zImage. The benefit of this is that it will not wipe out any of your user's data. The downside is that the user may be responsible for going into Recovery on their own and executing any steps your EDIFY update-zip would have typically taken care of, like clearing the Dalvik-cache.
==================
For now, that pretty much sums it up! I can expand on this, or perhaps more appropriately compress it (I am a tad verbose!) based on feedback and how useful this little guide ends up being for everyone. Let me know -- PM me or post here in this thread, I'll see it either way!
reserved post
reserved 3
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Odined back to stock. Loaded full wipe 3.2 and everything is golden. MMS, WiFi etc works great.
Did have to restart before WiFi would start. ROM is a little laggy at first but once it settles performance is on par with other JB Roms:thumbup:
Thanks Mr.GeeWiz: looks great for a "beta"
Edit: speakerphone works great also, sweet^o^
Sent from my SCH-I500 using xda app-developers app
I still think in overall the ROM is laggy.
WiFi requires restart each time you switch it off.
Whatsapp is not working after SMS code verification.
Thanks DJP952
i decided to give this a try. everything works great. wifi did not require a reboot for me. camera, mms, wifi all work great. a little sluggish getting started, but pretty stable nonetheless. great work DJ. thanks
djp952 said:
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Click to expand...
Click to collapse
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
I can duplicate the Wifi issue and am looking into it. For me, it just took a REALLY long time for it to turn on, like 10 minutes. I think I know what I've done that might cause this and hope to fix it Getting the logs now.
edit: I think I see what the problem is, not sure why it hasn't been an issue with the "Media" version. I have to dynamically load and unload the Wifi driver to prevent bad things from happening, this isn't the usual way it's done. The OS is set up to start the Wifi "supplicant" automatically, when it probably shouldn't be. The supplicant can't load if the wifi driver isn't up yet. Sometimes it works, sometimes it doesn't, and when it doesn't Wifi will be hosed until the OS sorts it out. I have two solutions to try, the first is to see how Android behaves if I don't allow the supplicant to be started as part of the "main" service class, the second is to figure out that aforementioned bad thing and do it more properly. I'll get it. Sorry for the bug
Thanks for trying this guys! I never expected it to be as good as the "big" ROMs, and I wish I could do something about it being so ungodly slow for a while. It seems to pick up and work properly after all the apps have been updated and it's had a chance to do all the Google backups and whatnot that it wants to do.
One problem I saw yesterday for the first time that you might need to watch out for ... The battery TANKED in a matter of 2 hours for some reason. It looks like Google Search went off the reservation. I've also seen "GPS Status and Toolbox" destroy the battery if you don't close it all the way (long-press HOME, then swipe it away).
Oh, one cool feature we have now ... "Take Bug Report". Check in Settings/Developer options to see it. What this does is collect all kinds of logs and information about the phone and make an e-mail out of it. The default sends it to your GMail account. It's about 3MB, but it will be nice to have something everybody can use to gather logs for problem resolution rather than asking folks to hack around in ADB. So, if you run into weirdness, you can click that button, wait a while and watch scary "shell has been granted superuser permissions" pop up a lot, and you'll ultimately end up in GMail with something you can send you me or post parts of here! Great that Google added that in an accessible way finally!!
For the folks having trouble with turning Wifi on and off, I have an experimental/test patch for you. This patch will replace the GeeWiz 3.2 kernel with an updated version that changes the ramdisk/initramfs such that the wifi services are not started until Android requests them to be started. It may affect Wifi and Bluetooth Tethering, but my testing of the change here for both showed no ill-effects:
GeeWiz 3.2.1 Wifi Patch [Experimental] [EDIFY update-zip]
REMOVED: Please use official patch in the DOWNLOADS section of the main post
NOTE: You will be asked to re-opt-into the Google Location service on the first boot, this is normal. I clear the "Google Services Framework" app on any kernel change now to avoid the well known Jelly Bean issues with losing connection to Google Services when you alter the kernel. This may have been fixed with JZO54K, but why risk it when all you have to do is click "Agree"
You may have to reboot once more after installing this to clear up the Wifi on/off problems so that the Android settings are synchronized with the changes. If after a second reboot this does not solve your problem, please let me know!
Rollback: This change can be rolled back by installing the EDIFY update-zip for GeeWiz 3.2 again on top of it without wiping data. I can also package/provide a more specific rollback that only undoes the changes if necessary.
Please let me know if this solves your Wifi issues or not, so that I can either post it as a primary patch for GeeWiz 3.2 (and GW Media 3.2) or take another crack at solving it Thanks!!!
djp952 said:
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
Click to expand...
Click to collapse
Hi!
Wiped data dalvik and cache & now I am on JellyBean. Thanks djp952. :good::good::good:
This Rom looks great and apart from the Wifi issue ( havent got time to update my phone with the patch for wifi issue as yet) which takes some time to start or sometimes just rebooted my phone altogether, everything seems to work fine. Had a problem verifying Whatsapp but used their "Verify by Call" method and now its working fine too. Battery life seems good to me as of now. Liked the inbuilt BLN.
Sadly, as i mentioned before, i lost my 1x/3g connectivity (nothing to do with this Rom) and thats Ok for a day or two till i try & figure out something to enable it again. By the way, i have always done the wipe through recovery only. Never used the factory reset option in settings menu. And that means the 1x/3g settings get wiped out the moment I wipe Data (note: wiping dalvik & cache does not affect it).
Anyways , looking forward for more developments on this rom from you.
edit... The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
QuickPic
swapnilss said:
The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
Click to expand...
Click to collapse
We are a little off topic, but... I too have had nothing but problems with the stock Gallery application... not loading at all, not showing pictures, generally being grumpy (okay, so I get that way too sometimes), etc.
Try Quickpic (http://market.android.com/details?id=com.alensw.PicFolder) , it's a free app that is a gallery replacement (ad-free too!). Just make it the default and you should be set. If, for some reason, you don't like it... Just uninstall and revert back.
As for the Jellybean ROM... too sweet! I love having an original Galaxy S with JB running on it! I get questioned all the time what phone I have, because it's running the latest Android build and doesn't look like any out there right now.
Sent from my SCH-I500 using xda app-developers app
I'll load up some huge amount of photos and have a look at Gallery. I could switch from using the Google Nexus version to the AOSP, if it shows any improvements. One bonus we could get there is that I enabled widescreen photos in the AOSP branch Didn't include it for various reasons, one I recall was that it would crash if you tried the "face detect" option.
I'll have a look -- maybe it can be fixed! I also have to download this "Whatsapp" that people are using ... never heard of it What does it do?
Thanks as always for the feedback guys! Glad it's going pretty well thus far
FYI for any aspiring developers, I've started making a "HOW TO" guide for building GeeWiz from scratch in Post #2:
http://forum.xda-developers.com/showpost.php?p=33011164&postcount=2
I've gotten as far as how to make the AOSP ROM and compile the kernel. At minimum, I need to add how to make the ODIN files as well, but maybe later. Depending on level of interest, I can go into as much as anyone wants there, short of how to make actual code changes (but I could try to help offline). I think describing how to get from source to the flashable files is a good first step, I'll see how it goes from there
DJ, you should link this on the home page of GeeWiz 2.9, so more folks can get this. Also, I think you should name it JellyWiz...
Can I ask what this is ?
AndroidGee209 said:
Can I ask what this is ?
Click to expand...
Click to collapse
JellyBean for the Fascinate, with GeeWiz recovery and kernel
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
where can i find the compass?
CM Wiki, CM Google+, Fireball Wiki, Fireball Google+
Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2
Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems
Introduction
This is CyanogenMod 10.1 (cm-10.1) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.2.2. Usage of this ROM indicates that you understand...
the warranty on your device is void;
the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).
Preparations and Installation
Get your phone ready for a new ROM
You must have an unlocked bootloader or be S-OFF (read here for instructions)
Before leaving your stock based ROM, turn on all GPS location services:
Settings > Location > (all three location services) = On
Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
Install a custom recovery: CWM or TWRP
Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
Perform the factory reset function in recovery and wipe the /system partition
Flash the CyanogenMod zip and optionally flash the GApps version corresponding to CM 10.1.x
If you are S-OFF, you're done; reboot and enjoy
If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands:
Code:
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Updating to a new build
Make a backup of your current build in recovery
Install the new build
If you are S-OFF, reboot
If you are not S-OFF, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.
Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
SIM card added: the first couple times you boot the phone you may get a notice, "SIM card added". Do not hit restart, just hit the back button and the notice will go away.
Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.
Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
If your display flickers noticeably after an hour or so of usage, discontinue use of these official releases (see below for unofficial releases that do not exhibit this issue). This issue affects about half of the fireball user base (rough estimate based on forum replies). These builds use linux kernel 3.4 which was never released by HTC for the fireball, so the board files are assembled as best possible with what little we have for reference. If your device suffers from this problem, you may notice the flickering persists for a few hours after restoring another ROM, but it should eventually subside. The developer(s) are not responsible for damaged devices as a result of running these builds. Stick with a stock-based ROM if you're uncomfortable with this.
Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.
Most recent builds: goo.im
Archive/Mirror: mediafire.com
goo.im folder structure: visit the page to read release-specific notes
mdm-releases - Recommended for users that have flickering panels on official builds. Based on CM 10.1.2 stable using linux kernel 3.0
kernels - Enhanced kernels for use only in CM
cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases
GApps
Download the GApps version corresponding to CyanogenMod 10.1.x
Reporting Issues and Getting Help
Policy on bug reports:
You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
logcat or GTFO
If these steps are not taken, your report will be ignored.
How to gather helpful data for troubleshooting
How to use the issue tracker
Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.
Change Log
CyanogenMod BBQLog
fireball-specific changes:
20130725 - fix blank MMS messages from iPhone 5 users
20130723 - fix low in-call volume and raise speaker volume max
20130721 - fix signal strength reporting zero on some GSM networks
20130715 - fix front facing camera face detect crash, fix dim screen on wake
20130628 - wake-on-volume fixed
20130622 - camcorder can now record in all resolutions
20130619 - finishing touches to battery parameters; charging should properly reach 100% now
20130618a - stereo audio fixed
20130618 - fix charging and battery level indicator
20130616 - kernel 3.4 introduced, updated adreno driver blobs from Qualcomm
---- break all teh things ----
20130504 - wake-on-volume fixed; flash and shutter synchronized better in camera
20130424 - encryption of /data partition is now supported, read post 3 for instructions!
20130306 - fix for selecting bands crashes com.android.phone, SMS/MMS behavior changes
20130303 - camcorder video focus improvements (still loses focus, but should be better)
20130226 - all resolutions save without restarting camcorder application
20130223 - all resolutions available in camcorder (with quirks)
20130221 - secure adb, experimental microphone noise suppression fix (amluto)
20130217 - camcorder saves videos correctly
20130209 - gooManager OTA support, camera focus fixed, notification led fixed
20130207 - fixed audio applications freezing phone, sending mms messages should not return invalid destination, battery charging LED can be disabled
20130204 - removed non-effective VZW APNs, enabled MTP support
20130131 - experimental VZW APN configuration
20130128 - initial Release
Click to expand...
Click to collapse
Known Issues
Official Builds
Display flickers and gets worse the longer the phone is on (may not occur depending on specific panel in your phone) - if you experience this issue, discontinue use of the CyanogenMod nightlies until the bug is fixed
Screen-on delay is long
Audio pauses briefly during screen on/off events
High pitch background noise in camcorder recordings
Touch to focus doesn't work
Flash crashes camera application
The first few times the phone boots there may be a "SIM card added" notice
Workaround in post 3
Unofficial MDM Builds
Moving between 1x and LTE networks sometimes requires toggling airplane mode to get data working
Camcorder does not stay focused
Music lock-screen widgets sometimes flicker when you turn on the screen; the controls are still active though
The first few times the phone boots there may be a "SIM card added" notice - Workaround in post 3
Known Issues that will not be fixed
OTG mounting of USB sticks - Likely no hardware support
FM Radio - Likely no hardware support
MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
Workaround in post 3
Development Information
CyanogenMod 10.1 builds using linux kernel 3.0 were becoming very stable before DxO Labs made a DMCA take-down request on a camera auto-focus library: libDxOAF.so. CyanogenMod had to pull official support for this device until builds could be offered that do not include this library. Kernel 3.4 no longer depends on the auto-focus routines in that library, so development efforts have gone into getting evita, fireball, jewel, and ville running well on it. Official nightlies are currently available for fireball, based on kernel 3.4, but there are a number of issues to be resolved (see above). Since HTC has not released an official jellybean ROM for this phone, there is no recent kernel source that could provide hints about how to fix these issues. If you have kernel development experience, your help would be greatly appreciated in fixing up the board files: android_kernel_htc_msm8960/arch/arm/mach-msm/htc.
The following trees are needed to build CyanogenMod 10.1 based on kernel 3.4:
CyanogenMod/android_device_htc_fireball
CyanogenMod/android_device_htc_s4-common
CyanogenMod/android_device_htc_msm8960-common
CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.1 build to pull necessary proprietary files into vendor/htc.
The following trees are needed to build unofficial CyanogenMod 10.1.2 based on kernel 3.0 (a.k.a. mdm-releases):
mdmower/android_device_htc_fireball - branch cm-10.1-FbR
mdmower/android_device_htc_msm8960-common - branch cm-10.1-FbR
mdmower/android_kernel_htc_msm8960 - branch cm-10.1-FbR
mdmower/android_frameworks_base - branch cm-10.1-FbR
mdmower/android_frameworks_opt_telephony - branch cm-10.1-FbR
mdmower/android_apps_Settings - branch cm-10.1-FbR
Use the extract-files.sh script in the fireball device tree while running an unofficial mdm build to pull necessary proprietary files into vendor/htc.
Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
htc-msm8960-devs: a talented group of developers with lots of patience while I was learning
utkanos, KemoNine, and Jin^eLD for general building questions
jose51197, Linch89, and blazingwolf for early testing reports
squeezyb for selling his fireball at a discount so I can share it with other developers
Restoring a borked radio
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
FAQ and Workarounds
The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!
Stuck at the HTC boot screen (solution by Aldo101t)
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times
Screen flicker
If after leaving the phone on for a few hours you notice the screen flickering rapidly, it is advised that you stop running the offical builds and restore a stock based image or one of the unofficial CyanogenMod 10.1 mdm-releases. You may still notice flickering for an hour or two after switching to a different ROM, but it should eventually subside.
"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).
"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Network mode = LTE/CDMA/EvDo
CDMA subscription = RUIM/SIM
Do you have suggestions for other carriers and/or other countries? Let me know what settings work for you, as well as necessary edits to build.prop.
Missing menu button in applications (solutions by blazingwolf and somerandomname1)
Option 1: Re-associate the recent apps button: Settings > System > Hardware keys > Enable custom actions > App switch key
Option 2: Use action overflow: Settings -> System -> Hardware keys > Show action overflow
Text messages from 6250 with message VZWNM: # (solutions by Linch89, MJL99, and slacka-vt)
See this thread and this post.
ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.
Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/
ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.
Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.
MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP
Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install gvfs
Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.
"I'm running RC1 or RC2 and I refuse to update!"
At least apply this small update package to fix low power audio and update the RIL to comply with changes to Verizon's network.
GPS doesn't acquire a signal (solution by somerandomname1)
From recovery, make a nandroid backup of CM
Wipe data, cache, and system
Restore a stock-based ROM backup
Enable all location services: Settings > Location > (all three location services) = On
Use a GPS application to get a lock on your position (I use GPS Test)
From recovery, wipe data, cache, and system
Restore CM backup
Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
Restart the phone to recovery and connect the USB cable to a Windows computer
In recovery, use the mount USB feature:
ClockworkMod(-based): mounts and storage > mount USB storage
TWRP: Mount > Mount USB Storage
When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
Your /sdcard partition should now be accessible
Encryption (thanks to Slick1123)
Pre-requisites: TWRP 2.6.0.0 or newer
Encryption procedure:
Make a full backup in TWRP
Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
Reboot and let phone battery charge to 100%
Turn on Airplane mode
Settings > Security > Encrypt phone
Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
Wipe your data partition
Restore your backup
Using the Droid Incredible 4G LTE on non-Verizon carriers
Remove the following lines from build.prop:
Code:
# Carrier definitions
ro.cdma.home.operator.alpha=Verizon
gsm.sim.operator.alpha=Verizon
gsm.operator.alpha=Verizon
ro.cdma.home.operator.numeric=311480
gsm.sim.operator.numeric=311480
gsm.operator.numeric=311480
# Access to Verizon/HTC apps in Play store
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-verizon
Congrats on getting this working.
+1 this is what is making me keep my phone
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Love cm10, congrats on the work.!!!
Sent from my Incredible 4G LTE using xda premium
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Great im happy to tell i have run this like for 3 days great battery exelent performance and I'll post over clock for this soon
Sent from my Incredible 4G LTE using xda app-developers app
With this version I have the following issues:
1. Apps don't have menu buttons. I had to change the recent apps button to open/close menus to get menus working.
I am not S-Off as I couldn't get that to work for me but I have the unlocked bootloader.
blazingwolf said:
1. Internal sdcard is not mounting correctly. It shows as not mounted in Root Explorer and Gallery, Camera and other apps that need it complain that it is not there. What's interesting is Settings/Storage sees the internal storage.
Click to expand...
Click to collapse
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
mdmower said:
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
Click to expand...
Click to collapse
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
mdmower said:
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
Click to expand...
Click to collapse
Yep, sure did.
sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Aldo101t said:
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
Click to expand...
Click to collapse
Im using another sdcard mod forma this ROM ill upload tomorrow by no ill just attach the file needed for that
Uploaded to drop box since xda app can't do it
http://db.tt/XPJ59Ux0
Sent from my Incredible 4G LTE using xda app-developers app
jose51197 said:
Im using another sdcard mod forma this ROM ill upload tomorrow
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
thanks JOSE
blazingwolf said:
Yep, sure did.
sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.
Click to expand...
Click to collapse
Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).
Aldo101t said:
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
Click to expand...
Click to collapse
When you wipe /system you wipe out this mod.
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
mdmower said:
Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).
Click to expand...
Click to collapse
I usted twrp no problem
Sent from my Incredible 4G LTE using xda app-developers app
Twrp no prob in root explorer internal shows as SD card and SD shows as external_sd
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.
blazingwolf said:
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.
Click to expand...
Click to collapse
Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.
Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls
mdmower said:
Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.
Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls
Click to expand...
Click to collapse
It won't mount. Tried both CWM and TWRP. They both say unable to mount sdcard.
Still working on it.
Hmm. Windows wants to format something.
I'm trying to encrypt the storage on my HTC One, but when I kick off the encryption task it just sits at the Android "gear-droid" (what I call the funny Android encryption logo, the one with the gear) until I manually restart the device. Encryption never takes place.
Running logcat on the device shows the infamous error:
"Orig filesystem overlaps crypto footer region. Cannot encrypt in place."
Searches on CM's issue tracker shows this open issue which discusses the problem at length, basically for this type of device the problem is almost certainly a misconfiguration of the fstab files. Essentially, they're set to use the last 16kb of the data partition to store the key in, but the partition isn't setup to reserve this space.
(XDA won't let me post the link, so go to CM's JIRA and look for bug CYAN-87)
A change was pushed to the Evita branch to fix this, but I haven't found a similar push occurring on the HTC One branch.
(XDA won't let me post the link, so go to CM's review board and look for change 48090)
I've been trying to run some of the commands referred to in the JIRA thread from recovery, but the file system presented to ADB there looks a lot different than the one at run-time, and it can't find any of the tools needed to do the job (vdc, make FS, etc).
Two questions:
1) Can this be fixed after ROM install? I'd rather not have to rebuild the ROM to fix this minor issue (reformatting is fine though)
2) Where are all the file system tools during recovery? I don't quite get why the recovery file system is so different than the normal run-time one, let alone where all the tools disappeared to
And if someone with the proper accounts / permissions could remind CM and the various device maintainers about the broken encryption support that would be swell. It seems like a lot of devices have mis-configurations preventing encryption from functioning, which is dangerous given how much access these devices have today (and how prevalent cell phone losses / thefts are).