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.
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
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance
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
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately