Related
DiscontinuedI'll make this short and sweet. Thanks to RaiderX303 recent work porting over clockwork recovery we can now flash roms in the update.zip format directly from sd with no need for a pc to flash a new rom. This allows most importantly the ability to to create Nandroid backups and restores.
Using RaiderX303 method I repacked my favorite ROM into a zip package ready for Clockwork Recovery.
Rom is Kouno.Takaaki's HD2ONE 0.3.6. This is based on his original release and everything should work just as it did before on this rom.
Please don't ask questions as to why this doesn't have xyz, or sense this or that, this is a close to stock vanilla android mod, if you want pretty sense skins, or don't like the way it looks, then get a sense rom.
His original thread http://forum.xda-developers.com/showthread.php?t=823471
Intrid.gz is updated to his newest version as of 1.2, details here http://forum.xda-developers.com/showthread.php?t=898067
Kernel is now Prj's .3, which is based off Hastarin's 8.6, modified for nand use. Feel free to update using the method in the Intrid.gz thread if you want a different kernel.
First you need to install clockwork recovery which has been ported by RaiderX303...
http://forum.xda-developers.com/showthread.php?t=898913
Then ...
How to flash;
1: Boot into Clockwork Recovery
2: Select install zip from sdcard
3. Select choose zip from sdcard
4: Select ROM file (HD2ONEupdate.zip) and then confirm
5: Wait for All Done! message
6: A wipe is recommended but not always required, if you experience force closes or things not working, try wiping before posting problems.
Please remember, I am not the original chef for this ROM, I have only repacked it into a format suitable for clockwork recovery so keep questions related to the underlying rom to the original forum. Also if you haven't read anywhere else, when you switch over to clockwork recovery method your userdata will be wiped so backup accordingly.
Download Link:
V. 1.2 http://www.multiupload.com/86KDPU1BXO
Wifi Tether App: http://www.multiupload.com/XVVRIFG83F
V. 1.1 http://www.multiupload.com/UR329DN289
V. 1.0 http://www.multiupload.com/06Q70SASLA
Changelog:
Version 1.2 01/07/2011
-Problems with intrid.gz not recognizing /.data/config.txt should be resolved. Changes to config.txt should now work properly.
-Kernel updated to prj's .3
Version 1.1 01/05/11:
-Updated Intrid.gz to Kouno.Takaaki v1.1 Ramdisk(should make update systemfiles,kernel,etc easier) See original thread for more details http://forum.xda-developers.com/showthread.php?t=898067
-Added Google Talk app and Google News/weather widget to systemapps as not downloadable from market, for all other google apps, ie. gmail,youtube, etc, download the newest version from market.
-Small modification to default MMS settings for Tmobile US users to fix mms send issues. If creating new data img settings will load by default, otherwise goto settings,wirelessnetworks,mobilenetworks,accesspoint names, menu button, reset to default, this will get you updated mms settings for tmobile us.
-If coming from 1.0 you should be able to do a no wipe update in recovery without problems.
Verson 1.0 01/04/11:
- Initial Release
Credits to;
Kouno.Takaaki for his Rom
RaiderX303 for his work on porting Clockwork Recovery
Cotulla + DFT - For MAGLDR and all the great work thats gone into NAND on the HD2
CyanogenMod Team - For the great recovery that allows flashing custom roms
Anyone else who has contributed to android on the HD2
Thanks, wanna try..
What a beautiful day
what initrd and zimage did you use for this rom.zip?
thanks..
rmnet or ppp? thanks!
Hi, I try to change the density with 200 in /system/build.prop. But it is not work when I restart my phone?
Is there a problem? I saw that the rom is based on CM build. But I can change it on CM 6.1.1 build. Could you please help me to take a look?
flashed fine but then just sits at the green htc screen...
did hard reset..same thing...boots to green htc screen.
thnx to titanium backup im back where i started 15 mins later
Does it support data.img on sdcard?
tried this but getting a nand kernel open failed when magldr tries to load the rom any ideas?? Do i have to supply my own kernel??
Ricey
Ok to address some questions and issues.
Build is RMNET, again based on original Nand HD2ONE.
Kernel is proj .2 which is based off of Hastarins Kernels.
Intrid is also from HD2ONE nand build so... it supports data.img to sd (off by default), therefore you must create a folder in the root of your SDcard and do the following:
Name folder. ".data"
Inside ".data" , Name a new txt file "config.txt"
Then you can add any of the following lines:
data2sd=0
- default nand userdata
data2sd=1
- enable data.img support
data_size=512
- size of data.img, only work when data.img support enabled
- default 512
lcd_density=240
- change the size of icons
- default 240
gps_zone=us
- country code, us, fr, jp, etc
- default us
As for people having issues booting or getting stuck at green htc, I would give a few pointers, if first boot then keep in mind the build is creating a new data file and first boot could take 10 minutes, so be patient. Second if getting issues with magldr saying it can't load a particular file/kernel, you probably had a bad flash and I would start by doing a wipe within clockwork recovery and reflash.
bigfoots1 said:
flashed fine but then just sits at the green htc screen...
did hard reset..same thing...boots to green htc screen.
thnx to titanium backup im back where i started 15 mins later
Click to expand...
Click to collapse
Fix permissions after flashing could help
Works just as HD2ONE should - flawlessly Thanks a lot
ok, I thought i had waited 10 minutes...
wasnt sure if it was building or not.
i will try again and wait it out.
like i said titanium backup to the rescueif needed anyway...
Thank you!
drewestate said:
Ok to address some questions and issues.
Build is RMNET, again based on original Nand HD2ONE.
Kernel is proj .2 which is based off of Hastarins Kernels.
Intrid is also from HD2ONE nand build so... it supports data.img to sd (off by default), therefore you must create a txt file in the root of your SDcard and do the following:
Name new txt file ".config" (without quotes)
Then you can add any of the following lines:
data2sd=0
- default nand userdata
data2sd=1
- enable data.img support
data_size=512
- size of data.img, only work when data.img support enabled
- default 512
lcd_density=240
- change the size of icons
- default 240
gps_zone=us
- country code, us, fr, jp, etc
- default us
As for people having issues booting or getting stuck at green htc, I would give a few pointers, if first boot then keep in mind the build is creating a new data file and first boot could take 10 minutes, so be patient. Second if getting issues with magldr saying it can't load a particular file/kernel, you probably had a bad flash and I would start by doing a wipe within clockwork recovery and reflash.
Click to expand...
Click to collapse
15 minutes and counting...still sitting on green htc screen...
please explain...
if there are extra steps needed then why isn't that mentioned prior to this?
schremer said:
Fix permissions after flashing could help
Works just as HD2ONE should - flawlessly Thanks a lot
Click to expand...
Click to collapse
Since this incorporates Clockwork Recovery, can this now be used to swap kernels as well?
25 minutes at the green htc screen. I think its safe to say this has nothing to do with the data file be created. it doesn't work.
followed instructions, it flashes the zip and after reboot it just sits at htc screen...
I think im done messing with this untill i see others who have actually got this to flash and boot properly...
if there is another step then please state it...nebulous comments like "change permissions" are useless
Thanks..
bigfoots1 said:
please explain...
if there are extra steps needed then why isn't that mentioned prior to this?
Click to expand...
Click to collapse
It depends Owning android phone before used to fix permissions after flashing.
Sent from my HTC HD2 using Tapatalk
This build is freakin good
But I have a little problem with me settings.. if I want to go to settings -> sounds the whole settings fc
Tried it with fixin the permissions in the CW mod, but didn't work.. someone else has this issue?
lol..so basically your talking out your ass?
schremer said:
It depends Owning android phone before used to fix permissions after flashing.
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
bigfoots1 said:
lol..so basically your talking out your ass?
Click to expand...
Click to collapse
I'm not sure if understood you right. Anything personal?
This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Galaxy S.
All Samsung Roms are running ontop of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you're not able to flash any kernel or run any filesystem you want. Use it as it is.
Only data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix").
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from earlier CM7?
Do a Nandroid Backup!
Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=galaxysmtd
Compatible Radio Images (>= Nightly 15): http://codeworkx.de/download/cyanogenmod/
Supported devices: GT-I9000, GT-I9000M, GT-I9000T
before flash is recommended to check the md5sum
FREQUENTLY ASKED QUESTIONS:
http://forum.cyanogenmod.com/topic/24169-faq-cm7-on-the-samsung-galaxy-s/
CYANOGENMOD WIKI:
http://wiki.cyanogenmod.com/index.php?title=Samsung_Galaxy_S
HOWTO BUILD FROM SOURCES:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_GalaxySMTD
ADDITIONAL INFORMATIONS:
Maintainers:
- atinm - http://twitter.com/atinm
- codeworkx - http://twitter.com/codeworkx
- coolya - http://twitter.com/dumdidum
- guiperpt - http://twitter.com/guiperpt
- unhelpful - http://twitter.com/unhelpfulone
Irc:
- Host: irc.freenode.net:6667
- Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
- Generic Changelog
- CyanogenMod Source Twitter
- Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
If You Have Any Questions, Please Refer To This
CM7 QUESTIONS & ANSWERS XDA THREAD
http://forum.xda-developers.com/showthread.php?t=1067074
Regards,
~drz
have i ever told you i love you? i'm pretty sure i have but i'd just like to tell you again. i'm sorry for this offtopic post but i'll edit it later to something useful. just wanted to show my affection.
This should be it since the beginning.
Clean thread. That's how I like it
Excited for the Coming Soon patch!
Reboot Recovery
Woah! Can't wait to try this.
The quick troubleshooting post.
This post contains a compilation of problems/issues and answers provided in this thread and earlier threads. Not all answers are tested by me and I will in no way guarantee that this wont mess up your phone.
You know, watch your kittens. They might be eaten by following the advice written down here.
DETAILED INSTALLATION INSTRUCTIONS CAN BE FOUND HERE.
rschenck wrote a very nice (and updated) guide for how you install CM7 on your SGS these days.
Things have changed quite a bit recently, so even if you installed it two weeks ago, you may want to check this one again.
What do people mean with "correct" bootloader? How can I make sure I have the right one?
Do NOT install directly on top of existing Samsung 2.3.3 firmwares or other firmwares based on this (like Darky's 10). Similarly, don't install directly on top of Eclair.
See this very easy guide on the android soul for flashing XXJPU, which is Froyo with the correct bootloaders needed..
I'm not sure I understand these procedures. Can you draw it out for me?
Anticipating this very question, rschenck actually did draw out a flow-chart for you.
See here.
But I'm not using the I9000, I'm using something else...
codeworkx provided a reference list you can check to ensure you are getting the right files.
After flashing the initial CM kernel I can't get CWM Recovery to work. It just displays some weird image
CWM Recovery might have different keymappings from the ones you are used to.
- Volume keys: Naviagte up and down in menus
- Power button: Select item
- Home key: Show/hide menus
If you are only seeing a weird image, chances are you've hidden the menu by pressing the home key. Try pressing it again
I can't find Cyanogenmod nightlies in ROM Manager
Yes. CM7 for the SGS is now mainlined and supports ROM Manager for nightlies, should you have the premium version. If you have the Premium version, follow these very graphic instructions to configure ROM Manager for nightlies.
To install from MIUI (courtesy of runedrune)
- Reboot into recovery using 3-button-combo
- Choose "mounts & storage" and format system, data, cache, datadata
- Do not apply the initial-file.
- Apply the latest update
- Apply the latest gapps (which can be obtained here. You want the one with -gb- in the name )
- Done. Reboot
Odin doesn't recognize my phone anymore and I want this fixed in case I mess something up
You will probably need the Nexus S drivers (which supposedly is really just some updated Galaxy S drivers).
If Odin for some reason don't see your device when connected, make sure the old Galaxy S drivers are uninstalled and removed. Bilboa1 gives some good hints about how to make sure your drivers are actually fully removed. Do check this before proceeding to install the Nexus S drivers.
After you have installed the Nexus S drivers, plug in your phone. Windows should now install some drivers, but you are not done yet. When using download-mode your phone will show up a little differently to Windows, so put your phone in download-mode and plug it in, with neither Kies nor Odin running. You will probably see Windows installing some more drivers.
After doing this, Odin should hopefully be able to recognize (and flash) your phone.
IS THIS "FOR EVERYDAY USE" NOW?
It depends. If you have to ask, it probably isn't.
I've flashed this and decided it is not ready for me. How do I flash back to stock ROMs?
Get the appropriate firmware you are interested in, flash as usual using Odin, but check re-partition and use the 512 pit-file.
For pre-rooted stock-images, you can use EZBase as shown here (also includes download links).
OTHER STUFF / KNOWN ISSUES AND SOLUTIONS
Please take a look here to see if your issue is mentioned and has a known solution before posting.
After flashing CM7 I get strange colours on my screen during boot
You do not have the correct bootloaders. Basically flash 2.2.1 following this article and then redo the CM7 installation. All should be fine.
Guys! Guys! I cannot find Android Market!
Google stuff is not included in CM7 by default. Download and apply latest gapps from CWM. You want the "universal" one with "-gb-" in the name.
But I want the latest gtalk with video and all that fancy stuff
got_milk was nice and uploaded some stuff. Beware though that lots of people are reporting this to force-close a lot, and that's not just on SGS CM7.
Can I run Samsung apps like Memo, Camera etc on this firmware?
No. Sorry. All Samsung apps depend on TouchWiz libraries which can only be found in Samsung firmwares.
How do I get additional themes for CM7 themes chooser?
Check the themes forum here on XDA or search for "CM7 themes" on Android market.
Once installed, the themes will be available in the themes chooser yes. According to the devs should reboot to fully apply the theme, but if you want to avoid reboots Android market might have something for you.
Things used to work, I applied a nightly update and now everything force-closes
Try wiping cache and dalvik cache in CWM. You should do this every time you install a new update.
Does CM7 need a lagfix?
CM7 uses ext4 (for /data) and yaffs2 (for everything else). CM7 does not use Samsung's RFS which was the main cause of poor performance on Samsung firmwares.
So no, your system is already lagfixed, you don't need to apply a lagfix and according to the developers very bad things will happen if you try to apply one anyway.
My current ROM has a lagfix. Do I need to disable that?
Probably not.
If you have a 2.3.3 ROM with 2.3.3 bootloaders, you will want to do a full wipe to stock 2.2.1. See above. In this case you no longer have a lagfix anyway and don't have to worry about it.
If you have a non-2.3.3 ROM with a lagfix, you don't have to disable it. All your partitions will get wiped by the installer anyway and so will your lagfix.
For whatever reason, I want to flash a custom kernel
You can use custom-kernels, but CM7 is a work in progress with new kernel-revisions popping out with every release. Make sure you flash a kernel which is compatible with the nightly you are running. Also: Do NOT flash via Odin, flash via CWM.
rschenck has a very good post on this.
If all you want is a "voodoo kernel" for voodoo sound, just (buy and) install Voodoo Control Plus from the market. It will load the required kernel-modules while you can stay on the stock kernel, making the lives of the developers much easier should you encounter bugs.
Is it possible to flash my own CSC from recovery after installing cm7?
According to the devs, this should not be needed.
Flashing other modems/radios
(Courtesy of GrimVarg: http://forum.xda-developers.com/showpost.php?p=13399590&postcount=8117 )
Odin will not work and it might **** **** up. The reason is that Odin and heimdal does not understand the CM partition layout and will just write the modem where it thinks is should be. Overwriting other stuff in the process.. So you need to use the specific update zipfiles on teamhacksungs sourceforge page
Click to expand...
Click to collapse
Instead of using Odin, download radio-packages from the following link, transfer to your phone and flash via CWM:
http://sourceforge.net/projects/teamhacksung/files/galaxys/
I want to keep my 850 band, and I don't recognize any of the modems on the sourceforge page
Lorssoth says "use KC1" and robbiev80 posted some download links you might be interested in.
Does external SD card work with cm7? Thanks!
It does. Make sure you have the proper bootloaders before installing as mentioned in the first part of this post. EZBase can be used for this.
External SD card will get mounted as /mnt/emmc. This may not be visible to all apps. If you desperately need the contents visible to apps only looking in /mnt/sdcard, create an empty directory there and remount the /mnt/emmc there as well:
Using either the terminal emulator or adb shell:
Code:
su
mkdir -p /mnt/sdcard/external_sd
mount /dev/block/vold/179:9 /mnt/sdcard/external_sd
Note: This is only a temporary fix for when needed. It will cause issues when you try to use USB sharing later. Write the following to get things back to normal:
Code:
umount /mnt/sdcard/external_sd
USB sharing doesn't work
Try installing the Nexus S drivers, instead of the Samsung ones.
After installing this camera doesn't work
Try locking and unlocking your phone. No really.
After installing this I cannot get any data-connections apart from wifi
There is a problem with RIL (radio interface layer)-polling. Lock and unlock and you should be OK.
If this sounds cumbersome, mobilescooby claims that installing Juicedefender somehow fixes this for him and that he no longer needs any lock and unluck boot-rituals.
This issue should now be resolved.
After doing this I still cannot get any data-connection apart from wifi
You might need to configure APN settings. Normally your network-provider will have this information on their homepages and some even offer to send them to you over the network.
After installing this I cannot send and/or receive MMSes
See above: You might need to configure APN settings. Check your provider.
After installing CM7 I cannot connect to my wifi-network
It might be related to what channels you have enabled on your phone. If your wifi network is using channel 12 or higher, you may need to enable those channels on your phone.
Go to Settings/Wifi & Network/Wifi settings/Advanced/Regulatory domain. And try not to be in violation of local laws with regard to channel usage
After installing CM7 I cannot connect to 802.1x EAP Wifi networks
This is seemingly an issue with lots of custom kernels and even some of the Samsung Firmwares. Yours truly can't get it to work at all, not on CM7 nor Samsung's JVB firmware.
Other people have reported that forgetting the network and adding it manually, by entering the SSID (with correct casing) and filling in all the details themselves have solved their problems.
YMMV
After installing CM7 I cannot charge my phone to 100%. WTH
No actual firmwares allows you to charge the battery to 100%, but stops a little bit before it reaches that point. This is to protect the battery from overcharging and should (in the long run) give you much better battery-life.
While stock firmwares from Samsung shows that the phone is 100% charged, this simply isn't true and is just UI-candy to make you all feel comfy. It's really charged to something around 94-98 percent.
So if your phone stops charging around that point, everything is normal, and the only new thing is that your phone is no longer lying to you
My GPS performance is terrible
Welcome to the world of Samsung Galaxy S GPS flux. Things you can try to improve on this includes the following:
- Install faster fix from Android market. Ensure you have the best time-server for your area chosen.
- You can also try AngryGPS, which siberian tiger was nice enough to upload.
- If all else fails, you can also try to flash a radio with a good GPS reputation. For flashing radios, see the appropriate section of this post. For some detailed post about the different radios eeyunopper posted this link and this link. (With ZSJPG I am getting decent result, YMMV)
Auto brigthness is kinda not-worky
You can try the presets outlined by Arkymedes right here.
How do I configure proxy settings?
(Thanks to runedrune)
If you are used to looking for proxy settings under Settings/Wifi & Network/Wifi settings/Advanced, you wont find it there.
Using either Launcher pro/ADW Launcher or another launcher which lets you create shortcuts to activities:
* Long hold on some open space on your launcher
* Select (Custom) Shortcut
* Select Pick your activity/Activities
* Scroll down to settings and click this
* Scroll down the long list and you should find proxy settings
You now have a shortcut to configure proxies as usual.
This "headphones mic on mute + instant music after call bug" is really irritating
If you are using Samsung or Nokia headsets, this is due to a problem on their part. See Arkanius' post right here.
Other things I should be aware of?
- Don't use 2G/3G data-switching. Period. At least not while the data-connection is active.
Not trough widgets, tasker or any other means. Seriously. Should you do this, you might end up having to restore nandroid backups or doing factory resets.
This report has details on more sophisticated ways of cleaning up which may lead to less data-loss, although not everyone can get it to work.
*subscribes*
nice work with the GPIOs, camera and other parts !
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
eeyunopper said:
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
Click to expand...
Click to collapse
I've already notified the mods to close / lock the other one ...
Good job on the clean house, everything is working great on my phone and very speedy
Mortify1 said:
Good job on the clean house, everything is working great on my phone and very speedy
Click to expand...
Click to collapse
The same for me My phone is working so great and very very speedy
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
I'm waiting the upcoming improves on camera in great expectation.
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
no
after format system/data/cache
just apply the last update
runedrune said:
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
Click to expand...
Click to collapse
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Nice things are comming... I hope for battery improvemant and radio FM. Since we got GPS, Compass is not so important but nice additional that save battery/make quicker fix.
Codeworks, do you got any rodemap?
Tantrico I said:
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Click to expand...
Click to collapse
nope. just flash that file. i made the same switch from miui to cm7 two days ago
@codeworkx , if reboot in recovery works = nightlys updates for ROM Manager? !
Enviado desde mi GT-I9000 usando Tapatalk
FIRST THINGS FIRST:
This represents very little work that I've done on my own. It is mostly appropriating the work of others. The important thing to note is that the file works and it works well.
All I did to create this file was incorporate a modified version of stachre's updater-script into the official WiFi 3.1 update from Google (this is not the file you should flash).
I then added the kernel & all of the files from bigrushdog's HC3.1 .zip EXCEPT the system.img file (which is the vast majority of the update). BRD's HC3.1 installs the 3G version of 3.1 with Hotspot/Tethering options in the settings menu under Wireless & Networks, and I personally want to have the WiFi-only software on my WiFi XOOM. His version seems to work just fine and the only difference I noticed was in the Settings menu, but that was enough of a difference for me to prefer the WiFi only software. I'm sure more of you may feel the same. If there are any other differences between the WiFi & 3G software I'd be curious to know what, if any, there are.
I then added the code from BRD's updater-script (minus the parts relevant to flashing the system.img) on to the end of the updater-script from stachre's updater-script.
One of the benefits of this approach is that it does not require you to perform a factory data reset, as BRD's method currently does. And yes, you will have access to your external SD Card in the /sdcard/external folder.
It is super late and I am exhausted, but I wanted to share this with you before I fall asleep. If you seem to notice that these instructions are more or less copy and pasted verbatim from stachre's thread, that is because they are. This is a simplified version of his method with the addition of BRD's modified version of the stock 3.1 kernel for SD Card storage. There are fewer steps (now only 2) because more files are included in the zip.
[size=+1]DOWNLOAD HERE - FLASH IN CLOCKWORK RECOVERY:[/size]
MZ604_3.1_ROOT_update.zip
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk. If you're stuck in a boot cycle, try a factory data reset in recovery.
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (MZ604_3.1_ROOT_update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Pushes Superuser and su, sets correct permissions to enable functioning root
Flashes the system partitions to stock (required at this time)
Flashes bigrushdog modified stock boot.img (kernel) to enable external storage
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Leaves recovery intact
Outstanding Issues:
The new
Videos.apk does not appear in app drawer after update, according to Motorola this was done intentionally. Videos still play in Gallery. For some reason Motorola doesn't want us to use this app yet on the WiFi Xoom, but it's available on the 3G Xoom.
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the update here: MZ604_3.1_ROOT_update.zip
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola also available via torrent
You've flashed a recent version of ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Flash stock system.img & boot.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
The pre-update checks also include the boot partition. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
If you are unlocked and running unrooted stock Android 3.0.1, you can skip step 1. If you are already on 3.1 and just need root and/or external SD card storage, see this thread.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
You may need to re-enable USB debugging in the Application settings menu before you can send the above adb command. Alternately after sending 'fastboot reboot' in step 1, wait a few seconds after you see the Motorola logo and tap the Volume Down button. If you see "Android Recovery" at the top of the screen, tap the Volume Up button to boot into recovery and install from there.
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy MZ604_3.1_ROOT_update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "MZ604_3.1_ROOT_update.zip"
Select "Yes - Install MZ604_3.1_ROOT_update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulations! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
CUSTOM KERNELS:
I told you guys it wouldn't be long. TDR has already released an overclock kernel for WiFi Xooms on 3.1.
Tips & Tricks for quick-booting into Fastboot & Recovery:
Booting into Fastboot:
Hold down both the power button and the Volume Down button. Fastboot support will boot and you can flash system/recovery/userdata images.
Booting into Recovery:
I haven't seen anyone else mention this. If you power up, wait a few seconds after the Motorola logo appears, then hit the Volume Down button you will see "Recovery" appear at the top of the screen. Hit the Volume Up key to boot into recovery!
Great instructions, the simplest I could see so far! The above process worked for my WIFI only XOOM which I had rooted and installed the Tiamat Xoom Kernel. I am in Australia so was impatient to wait for OTA which probably wouldn't have worked anyways from what I have read.
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
it is different because no wipe is needed, if you are stock (unrooted) you will have to wipe when you unlock the bootloader
This is exactly the method I used, though I did thinks manually and it took a while, but works great
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Sent from my Xoom using Tapatalk
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
xoppaw said:
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
Click to expand...
Click to collapse
Yeah, the two main differences between this and BRD's procedure is that you don't have to perform a factory reset to get this one to work, and this method requires adb/fastboot. I don't think you should have to erase all your data just to install an official update. It's also only one file to flash.
The other difference is that this version doesn't have artifacts from the 3G version in the Wireless & Networks Settings menu (if that bothers you).
I don't know if this update would apply on an unlocked and unrooted Xoom, but if your Xoom is unlocked this version of the update should give you root. Both would be worth testing
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
tekuru said:
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
Click to expand...
Click to collapse
You can still play videos/local content fine through the gallery app, so we are safe in that respect. I can still watch all my movies or videos filmed on the Xoom just fine.
Here are some observations that I made. The WiFi update only included the Videos.apk file while the 3G update also included a Videos.odex file as well. I chose to add the Videos.odex to the update file in the OP, but it didn't make a difference (Videos apk still doesn't show in the app drawer).
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Land Master said:
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Click to expand...
Click to collapse
Thanks, I updated the OP to take account of that. Ever since I figured out how to boot into recovery from the Motorola logo I haven't really needed to send the 'adb reboot recovery' command.
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
kev0153 said:
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
Click to expand...
Click to collapse
Yes, I'm pretty sure for whatever reason the Videos.apk is enabled for the 3G version of 3.1 but not for the WiFi version of 3.1. I agree that the extra settings isn't a big deal, I made this file mostly because I wanted a way around wiping all of my user data.
Rumor has it that Google has said that the Videos.apk will be working on the WiFi Xoom in a few days.
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
IXIKelsonIXI said:
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
Click to expand...
Click to collapse
Download and flash this file:
http://www.mediafire.com/download.php?2bj5taicy3buc5c
Basically do what I said to do in the OP but skip step 1.
You are beautiful, and I love you.
I installed brd's 3.1 update yesterday, and i tried to install this zip over his method because i have a wifi xoom and wanted to get rid of the hotspot settings, but when i try to flash this in cwm i get an error:
Assert failed: file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.0.1/hwi69/110420:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/hmj37/124251:user/release-keys"
E: error in /sdcard/mz604_3.1_ROOT_update.zip
(status 7)
installation aborted
What is the problem? Is it not possible to flash this over his method? Do i have to change the build.prop?
Thanks
Edit:
Solved by going back to stock 3.0.1 and installing the cwm to get updated to 3.1.
WARNING Boot Loop!
Warning. This method set me in to a boot loop. The tip at the bottom of the instructions eventually saved me as I booted in to recovery (adb stopped working after awhile) and upgraded via bigrushdog's clockwork thread. Not sure if it was my custom boot theme or something else. I reflashed twice while adb was still working. All looked good each time but then when I rebooted to do the final cwm step, this is where I looped each time. I was careful. Not sure why it messed up.
Thanks a lot for putting this together, worked like a charm.
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
kntdookoo said:
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
ericdabbs said:
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
Click to expand...
Click to collapse
1. It's weird. My understanding is that even, unrooted stock WiFi Xoom owners can't access the new Videos apk on 3.1. The Videos.apk is there it just doesn't show up in the app drawer so there isn't any way to access it. If you look for it in a file manager like Root Explorer you can see it. There are other "ghost" apps like that in Android like the SoundRecorder.apk, so that's not completely unheard of. What's puzzling is why the 3G Xoomers got one that works and we didn't. If/when this is solved I will update the OP. It does work if you use bigrushdog's update method (but you gotta wipe all your data).
The Videos apk is mostly a showcase for their Video rental service that they announced Tuesday, you can still play videos in Gallery, so you're not really missing out on any major functionality at the moment.
2. The new features are cool! It's hard to compare performance since I was overclocked before and now I'm not. I love the resizable widgets. Overall it does feel like a more polished OS, they fixed a whole bunch of little itty bitty issues here and there. I can't really think of any downsides to the upgrade, it just feels like a step in the right direction. I'm definitely looking forward to see where Honeycomb development goes in the future.
I have installed this update over my rooted wifi only 3.0. It worked great, i did get a boot loop and was forced to wipe in recovery (luckily i did a titanium backup first), apart from that it went through no problem.
I haven't used the browser extensively yet, but it does seem more stable, hasn't crashed yet and the overall browser seems much better, especially the thumb menu from labs.
Good work!!
(I have the wifi only UK version BTW)
Hey Guys,
Being a new person on this forum, I was not able to post on the original thread, so posting here.
I have been on IceColdJelly421 - 1.6 - JellyBean 4.2.1_r1 for last 2 weeks and have found it to be an excellent ROM. However I noticed something very weird today.
My HTC ONE X's (international tegra) SDCARD is gone! when I connect to mac, I can only see my 2.11 GB internal phone storage, same from Settings -> Storage. I tried formatting the SDCARD (~27 GB) from TWN and mac (as FAT) but still it doesnt show up anywhere.
I also tried formatting the SDCARD from settings -> storage page, but that just keeps loading, nothing happens.
Any idea whats wrong here? I tried searching on the forum, but either didnt do a good job on it / didnt get anything
Please help / provide some input.
Update:
1) When I mount USB storage from TWN, i get a message on MAC that disk is not initialized. I format it as FAT from disk utility it works fine but then on reboot, I dont see in Android
2) Again from TWN when I try to format the SDCARD by using Wipe -> External Storage. The log says couldnt load SDCARD or something.
3) when "adb shell", I see my phone internal storage under /sdcard folder. Also I dont see any "0" folder inside my sdcard folder. As I understood from the IceColdJelly421 thread, 4.2.1 onwards, the SDCARD is mounted under 0 folder. But I dont see any.
-Rockingturtle.
Bump ! Any one ?
Have you flashed boot.img between different ROM versions? Because the boot.img in a particular version was bad and it was reverted in the following versions. Can't remember which though.
Try flashing boot from 1.6 for example, or 1.3.1.
I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock
rockingturtle said:
I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock
Click to expand...
Click to collapse
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock
rockingturtle said:
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock
Click to expand...
Click to collapse
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.
samooorje said:
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.
Click to expand...
Click to collapse
I tried that, but didnt work, the factory reset in TWR failed saying cannot mount /sdcard
When I flashed a different boot.img, TWR was able to mount and format the sdcard. Now I did a re-install of a different ROM (ARHD 18.1) and everything is working fine. Will try with ICJ again shortly. Seems like a lot of folks are reporting issues with 1.7.1.
-Rock
Just installed ICJ 1.7.2 by flashing the ROM from SDCARD, worked like a charm this time, both SDCARD and internal phone memory coming. Facing the following issues with the ROM currently.
1) The battery is draining faster, will let it settle for 1-2 days and then re-check. Will also adjust the brightness level, that helped a lot with 1.6
2) The rotation of home screen is still not working, I dont use that anyways , so no problemo !
3) Noted some disturbance / noise when doing a call in speaker mode. In earphone mode, it was crystal clear.
Thanks "Lord" and all the other team members for this !!
mputeop New
Just installed the 2.0 version from Lord...so far so good Thanks Lord !!
-Rock
Also trouble...
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!
bjornops said:
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!
Click to expand...
Click to collapse
#1 Yes, I have also faced this problem, the best is to restore HTC's stock ROM and recovery (this is important, as custom recoveries dont work) and then update. You can find the orignal recovery in the threads. People have posted them
#2 Did you follow the exact steps of booting into fastboot, adb shell and execute the commands from there? You might want to try a different boot.img for this. I used ARHD boot.img to do the changes and then got back to ICJ. I had to change my boot.img, because the ICJ was not showing my SDCARD at all.
Let me know if this helped.
-Rock
BTW on 2.1 ICJ now and loving it. I am facing some wifi, GPS issues. But that might be just because of my router (for wifi, as I had trouble connecting to my wifi even from mac, restart of router did the trick), for GPS / Signal, I noted low signal from carrier, so will wait for few more days.
Also noted that my soft keys are often skipping. The home button needs to be clicked twice at times. But in general and overall a very good ROM.
Thanks L0rd !!!
-Rock
Facing the following issues with 2.1:
1) The GPS fixing is taking a lot of time. I remember at office, I usually get a fix very quickly, but taking time now.
2) Post playing games (subway surfer), the device gets heated a lot specially around the camera area. This is draining the battery a bit.
3) Still loosing battery a bit faster than it did earlier.
4) The home button / associated vibrations dont register at times and I need to try them again. Also noted in subway surfer that game play is a bit jerky and some of my swipes are not registered. This might be due to any off: ROM, Kernel, Game, a poor screen guard.
Trying to get some data (logs etc) to substantiate the above observations. Might shift to ARHD for sometime to compare the data and provide better inputs.
-Rock
Installed ARHD, details captured here:
http://forum.xda-developers.com/showpost.php?p=38487569&postcount=39640
Yeah, I troubled the guys in their main thread after the HTC RUU exe surpriced me by erasing my SDcard, and mattoffshore gave me this link to a simple flashing tool: http://www.mediafire.com/?oik6tjvo28r9d
it worked out nicely, hboot 1.39 on .401. HTC__Y13 (tags for other unfortunate searchers)
ICJ 2.1 :good: until the next release any day now haven't had any big issues except a few camera FC and random hot reboots
-bjornops
I have changed from Rom from Android 11 to Android 10, and in the process the connection with the cell phone sensors has been lost. Investigating in Telegram groups about the RN8 I came up with the solution that was the following:
Code:
Fix for dead sensors
You might encounter the "Dead Sensors" bug when you flash a rom, DO NOT FLASH "persist.img" FILE!
But instead, do this workaround to fix the sensors without flashing anything.
INSTALL BUSYBOX FIRST
1) Open any Terminal Emulator app.
2) Type "su" to give it root permissions.
3) Copy and paste below command, apply it then reboot.
chcon -R u:object_r:sensors_persist_file:s0 /mnt/vendor/persist/sensors
4) Sensors should be working now, and this has been tested and it's working.
My problem is that since I made that rom change, the command files are not found so that I can solve the problem because those files have been deleted on my system.
I wanted to ask if someone would be so kind as to pass me the files of this root location:
/mnt/vendor/persist/sensors
same with me！i format all partions with some recovery，which i forget which one，since i tried all……
suddenly，sensors about display abnormal。
i tried fastboot mode to flash official ROM back，but do nothing to the dead sensor，very wired。
i thought i mistake formating some partion
Had the same problem almost a month ago.
*Spoiler* flashing the stock rom doesn't help.
The best way I found to fix it, was to use this solution.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
To make sure that something is wrong, run the CIT test.
If you don't know how to access it tell me