[size=+1]BEFORE YOU BEGIN[/size]
CUSTOM ROM AVAILABILITY: This is a stock rooted update (stock ROM, stock kernel), NOT a full-featured custom ROM; however, both 3G/4G and Wi-Fi users can enjoy Team Tiamat Xoom Rom 2.2.1 Moray. If you want the latest features implemented by Team Tiamat, install Moray; otherwise, if you want stock 3.2.1 HTK75D ROM and kernel with root, continue below.
COMPATIBILITY: This update is for the US Xoom Wi-Fi MZ604 ONLY!!! If you have a non-US Xoom Wi-Fi, this procedure may break your device. If you have a Xoom 3G/4G, this procedure may break your device. The update script performs NO CHECKS on the model of Xoom before flashing rooted stock 3.2.1 HTK75D system and boot images. This means it won't stop you from flashing on a non-US or 3G/4G device; it will just flash and you're left with the mess (if any). Please proceed only if you're tech-savvy with Android and the Xoom, ready to restore another ROM in case of issues, and good at troubleshooting. Please provide feedback and corrections, and I'll update the post as quickly as I can. Thanks!
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.
[size=+1]SUMMARY[/size]
This is a modded update package (update.zip) that updates the US Xoom Wi-Fi from any ROM to stock rooted Android 3.2.1 HTK75D using ClockworkMod Recovery:
Flashes bootloader from previous update (3.2.1 HTK55D) to ensure integrity
Flashes the boot partition with rooted stock 3.2.1 boot image, stock kernel
Includes a workaround for the Bluetooth tethering issue that was introduced in 3.2 (note: workaround is in boot.img, so flashing a new kernel/boot.img will overwrite it)
Stock kernel includes no extras (overclocking, etc.) from custom kernels
Flashes system partition with rooted stock 3.2.1 image (minus the recovery overwrite script)
Includes Superuser.apk 3.0 (new) and su binary to enable functioning root (thanks, chainsdd)
Hardware SDCard continues to be read-only via documented application permissions
Leaves existing recovery partition intact (stock 3.2.1 update overwrites it on every reboot)
Leaves user data intact (note: some users updating from custom ROM's recommend wiping data/factory reset to prevent issues)
[size=+1]PREPARATION[/size]
Download the modded Xoom Wi-Fi Android 3.2.1 HTK75D update package
update_US-Xoom-WiFi-3.2.1-HTK75D_stachre_v02.zip
MD5: A553FF238469A79D29AA042DCA1167C3
Ensure you have flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
Ensure a physical SDCard is installed in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
[size=+1]PROCEDURE[/size]
Copy/download the modded Android 3.2.1 Update package to the SDCard
Reboot into recovery
Reboot your Xoom
When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
Press the Volume Up button to enter Android recovery
Perform update
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also if you are coming over from a custom ROM, users suggest doing a "wipe data/factory reset" in ClockworkMod Recovery prior to performing the following steps.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the modded Android 3.2.1 update package
Select "Yes - Install <filename>"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom Wi-Fi, running on Android 3.2.1 HTK75D!
[size=+1]POST-UPDATE NOTES[/size]
Superuser.apk 3.0: Some issues are being reported; may be updated soon.
Bluetooth tether issue workaround: Implemented in boot.img, so flashing new kernel/boot.img will overwrite it.
[size=+1]CHANGELOG[/size]
v02: HTK75D update (Android version remains unchanged at 3.2.1)
v01: First release, HTK55D; includes root, Superuser.apk, su, Bluetooth tether issue workaround
[size=+1]UPDATE PACKAGE DETAILS (v02)[/size]
BOOTLOADER: flashed with stock 3.2.1 HTK75D bootloader
Extracted from previous update package (3.2.1 HTK55D)
Bootloader flashed after reboot
Code:
BCT[4->4] (vendor: 0x101 product: 0x5454 vers: 0x0)
RECOVERY: not flashed; left intact
BOOT: flashed with modded stock 3.2.1 HTK75D boot image with stock kernel
Unchanged from 3.2.1 HTK55D
Kernel: flashed with stock 3.2.1 HTK75D kernel
Unchanged from 3.2.1 HTK55D
2.6.36.3-g111d827 [email protected] #1
Includes no extras (overclocking, etc.) from custom kernels
default.prop: modded HTK75D default.prop (ramdisk)
Code:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ADDED: Workaround for the Bluetooth tethering issue
Issue introduced in 3.2 HTJ85B
Flashing a new kernel/boot.img will overwrite the workaround
SYSTEM: flashed with modded stock 3.2.1 HTK75D system image
build.prop: stock 3.2.1 HTK75D build.prop
Code:
ro.build.fingerprint=motorola/tervigon/wingray:3.2.1/HTK75D/190830:user/release-keys
ro.build.description=tervigon-user 3.2.1 HTK75D 190830 release-keys
REMOVED: Stock recovery install script, patch
ADDED: Superuser.apk 3.0 (new) and su binary to enable functioning root (thanks, chainsdd)
Hardware SDCard continues to be read-only via documented application permissions
USERDATA: not flashed; left intact
this will erase the tiamat kernel correct?
shakuyi said:
this will erase the tiamat kernel correct?
Click to expand...
Click to collapse
Yes. I suggest using this update only if you wish to have stock ROM and stock kernel with root.
EDIT: updated OP for clarity.
MORE EDIT: You can always re-flash a custom kernel after the update.
have you noticed any changes from 3.2 to 3.2.1?
Worked great, thanks
shakuyi said:
have you noticed any changes from 3.2 to 3.2.1?
Click to expand...
Click to collapse
I haven't been using it like a normal user yet, so I haven't noticed any differences. It's a small update, though, with the following files having notable patches/updates:
Bootloader
Recovery
Boot image (kernel 2.6.36.3-g111d827, also corresponding small update to bcm4329.ko)
/system/etc/security/cacerts.bks (probably response to DigiNotar debacle)
/system/framework/bouncycastle.odex
/system/framework/ext.jar
/system/app/NetworkLocation.apk
/system/lib/libskia.so
/system/lib/modules/bcm4329.ko (tiny update, probably due to new kernel)
In addition, a slew of system APK's, framework JAR's and ODEX's, and other miscellaneous files got touched, but the patches were so small that they're likely just version updates or minor bug fixes.
An official changelog (if we get one) would provide further clarification.
EDIT: HTK75D notable file updates:
Recovery
/system/app/Phonesky.apk (new Android Market 3.1.6)
/system/app/BooksTablet.apk
/system/app/BooksTablet.odex
/system/app/Music2.odex
/system/app/SystemUI.odex
/system/app/SystemUI.apk
/system/app/VideoEditorGoogle.apk
/system/app/VideoEditorGoogle.odex
/system/app/Videos.apk
/system/app/Videos.odex
/system/app/YouTubeTablet.apk
/system/app/YouTubeTablet.odex
/system/framework/ext.jar
/system/framework/framework-res.apk
i_am_the_one said:
Worked great, thanks
Click to expand...
Click to collapse
Just trying to be clear, sounds like this will update without effecting existing configuration and install. Is that correct?
Sent from my Xoom using Tapatalk
BigBadBuddy said:
Just trying to be clear, sounds like this will update without effecting existing configuration and install. Is that correct?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes data was not touched, everything was the same as before the update.
Thanks!
Sent from my Tweaked EVO using Tapatalk
i_am_the_one said:
Yes data was not touched, everything was the same as before the update.
Click to expand...
Click to collapse
One more thing. Did you flash Tiamat or any other custom kernel over this? Just wondering if the bootloader update in the new Tom would hose my Xoom with a different kernel.
Sent from my Tweaked EVO using Tapatalk
OK, just did this. Flashed this ROM, booted, rebooted into recovery, wiped cache and dalvik, flashed Tiamat Tachi, booted. Done. All good.
Sent from my Xoom using Tapatalk
BigBadBuddy said:
OK, just did this. Flashed this ROM, booted, rebooted into recovery, wiped cache and dalvik, flashed Tiamat Tachi, booted. Done. All good.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
I did not flash a custom kernal. I was running the rogue kernal before the update though. Have you noticed any issues running the tachi kernal? I would love to go back to overclocking, but I wasn't sure if the kernals would play nice with 3.2.1
i_am_the_one said:
I did not flash a custom kernal. I was running the rogue kernal before the update though. Have you noticed any issues running the tachi kernal? I would love to go back to overclocking, but I wasn't sure if the kernals would play nice with 3.2.1
Click to expand...
Click to collapse
Test it. Make a nandroid before you do so and give it a shot for a week.
Looks like that would break the bluetooth mod that was created though
Let us know how it works. I like the rogue kernel a lot.
i_am_the_one said:
I did not flash a custom kernal. I was running the rogue kernal before the update though. Have you noticed any issues running the tachi kernal? I would love to go back to overclocking, but I wasn't sure if the kernals would play nice with 3.2.1
Click to expand...
Click to collapse
Tachi works great. I'm typing this on my bluetooth keyboard (the only bluetooth device I have to test with). I'm going to test with Rogue later today. My concern initially was with the boot loader update on the 3.2.1 ROM. On the first kernels that I fflashed on my Xoom, there were custom boot loaders. I think they were only for charge lights onn/off, but wasn't sure. I'm pretty sure that any 3.2 compatible kernel will work with 3.2.1. The update was pretty small and mostly bugfixes from what I understand.
Sent from my Xoom using Tapatalk
the rogue kernel aborts before flashing I think due to version checks. But I flashed tachi , so we'll see how that works.
@bigdaddy I meant the Bluetooth tether feature. I imagine all else works great.
I installed this today and its great so far - thanks for your contribution.
Sent from my Xoom using xda premium
i_am_the_one said:
the rogue kernel aborts before flashing I think due to version checks. But I flashed tachi , so we'll see how that works.
Click to expand...
Click to collapse
You should be able to modify the installer script to look for 3.2.1
Sent from my Xoom using xda premium
does this update have a new market?
shakuyi said:
does this update have a new market?
Click to expand...
Click to collapse
Looks the same to me 1.0.28
Related
THERE WERE AT LEAST TWO REPORTS OF SYSTEM FAILURE AFTER THIS UPDATE, BOTH HAD LAGFIX ENABLED.
!!!BACKUP BEFORE PROCEED!!!
This guide is to help those who would like to test tegrak's kernel but have dowbts about losing ability to flash zip files from CWM. This will also help those who would like to have simple root solution, and 2e recovery on froyo.
a) If you want to have simple root solution, one click lagfix and 2e recovery. Tested with Doc's v9.1.4 but should work on any rom including stock
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market and install root from the app's menu
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
a) If you already rooted your phone
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
All this process replaces your 3e recovery with 2e recovery image and as tegrak's kernel does not overrides original recovery image your CWM will be untouched by tegrak's kernel, and you will successfully have combination of two recoveries (CWM and Tegrak's) To access CWM you can chose "reboot in recovery" from the Rom Manager menu or from Tegrak lagfix menu, and to access tegrak's recovery, press home button when you see tegrak's kernel introductory window while booting up your phone.
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
g00ndu said:
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think it's too advanced and dangerous for novices that mostly visit general. Also both described things 2e recovery and tegrak's kernel are from the area of development, this is all about customizing rom. I dont agree that it should be in general.
Thanks a lot!!
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
hensk said:
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
Click to expand...
Click to collapse
As I understand this fix didn't work for you, could you share to others what and how has failed?
Sent from my GT-I9000
no, no mate, just did not know that there is
thread like this,with fix solution
hensk said:
no, no mate, just did not know that there is
thread like this,with fix solution
Click to expand...
Click to collapse
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
brack11 said:
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
Click to expand...
Click to collapse
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
g00ndu said:
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
brack11 said:
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
Click to expand...
Click to collapse
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
g00ndu said:
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
brack11 said:
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
Click to expand...
Click to collapse
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
g00ndu said:
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
Click to expand...
Click to collapse
Yes, I used a few times to flash different modems and r64 theme.
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
fomofo said:
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
Click to expand...
Click to collapse
Did you have lagfix enabled? As I can say from my own experience.now - this hack is DANGEROS if you have lagfix enabled. To say more any manipulations with recovery while on onenand fix - DANGEROUS AND LEAD TO LOOSING ALL PARTITIONS
Sent from my GT-I9000
brack11 said:
Did you have lagfix enabled?
Click to expand...
Click to collapse
No, I have used the "hack" recovery 2e method with success right up until JPY, but JS3, and now JS5 does not work.
It seems to me (just learning Android), that it doesn't have write permissions to the /sbin directory, which is what the recovery script needs.
Recovery 2e works with CF-root, but I already have root, and rather not overwrite the stock kernel.
Ok, yesterday I have thoroughly tested my workarounnd for installing rom. I hade Doc's 9.6 downloaded 9.8 reboot into recovery using rommanager option, wiped cach partition, wiped dalvik, wiped data, flashed 9.8, wiped data again, and flashed again, rebooted, restored titanium backups, flashed tegrak's kernel, flashed update for recovery 2e from within tegrak's kernel, then rebooted into 2e recovery, flashed new modem (JVE) and flashed theme r64, rebooted, everything works as it should no errors no hangs no loops.
Does this still work?
Welcome!
Hello, these roms were made in order for people to have recovery-flashable zips of stock roms (not having to rely on tars and Odin). These roms are compiled from Odex and Deodex system dumps and have no other mods besides root, busybox and recovery.
***Disclaimer***
I am not responsible for any damage, be it mental, physical, mechanical, etc caused by the flashing of this rom. If you flash it, you do so at your own risk. Glad we could get that out of the way
If any developers want to use these as a base rom, there is no need to ask. Just grab em and go. I made these for themers and other rom developers who don't usually work at making the rom itself, but taking what's there and making it better. I hope it helps out!
First the shout outs:
CNZ (RoadRAGEN) - Updater Script, Odex & Deodex Dump
ptfdmedic - Deodex System Dump
bubby323 and chris41g - for use of kernels and general help.
k0nane - noCIQ mod.
thefredelment, phantomfreak53, darren.wsln1 and lballer59 - Help identifying issues.
And of course the Testers:
henbone11(WR47HANZ), COMEDY, lovinlissa1984, geraldweb, lballer59 and banksj174
The Goods:
Okay, the goods:
EG30 Stock Deodex with root, recovery, busybox WITH No CIQ
EG30 Stock Deodex with root, recovery, busybox WITHOUT the No CIQ mod
EG30 Stock Odex with root, recovery and busybox
The Download links:
Download links can be found here at the ACS Forums!
(Download links to prior versions are in post 2 over there)
Changelog and Features
Version 1 and 2 changelogs in the 2nd post
Changelog
Re-added bubby323's kernel so it is a pure stock rom with ONLY clockwork 5 recovery (no additional features) (all 3 roms)
Removed all non-stock apks and replaced all missing stock apks (only required for the deodex roms)
[/LIST]
Features
Android Version 2.3.4
Kernel Build: bubby323's stock with cwm 5
Rooted with SU v3.0 with fully updated binaries(thanks to cnz(RoadRAGEN))
busbox latest version(thanks to cnz(RoadRAGEN)
ClockworkMod Reocvery version v5.x (thanks to bubby323's kernel)
No-CIQ mod (one of the deodex roms only)(thanks to k0nane)
All stock apps/widgets included (I have removed nothing that came stock)
Pick Which SD Card You Want Recovery to Read
For now, the recovery on the kernels in these roms tells CWM to read from the internal memory card. If you want it to read from the external memory card go here and download the "Latest Compiled Version". Flash in Odin and CWM will work with the external sd card. These roms run the link under "Older releases".
Installation Instructions
For those who just wanna use it as their daily drivers, here's the installation instructions:
ALWAYS MAKE A NANDROID BEFORE YOU FLASH ANYTHING!!!!! <-----Words to flash by.
1. Download rom, put it on your phone.
2. Boot into recovery.
3. FULL WIPE IS REQUIRED. Data AND cache AND dalvik.
3.5 Go back and make sure step 3 has been completed
4. Flash rom.
5. reboot and enjoy
**Warning**
The flash process and first boot takes a minute. Be patient, it will work!
Known Issues
Okay, for whatever reason, the deodex w/NoCIQ just will not install the MyFiles.apk. This doesn't sound significant. However, without it, the contacts app will Force Close when you attempt to assign a custom ringtone to a contact. There are two workarounds:
1. Get a different file manager, navigate to the sound and manually assign it to a contact.
2. Find the apk (it's in every flashable rom) and install it onto your phone manually.
I will attempt to fix it once an update comes out and I'm forced to play with these roms again. Until then, the workaround works just as well. (thanks lballer59 for finding the problem).
Downloads for older versions found In the 2nd post on this thread
Changelog 10/04/11
Version 1's changelog is in the 2nd post.
Deodex WITH No-CIQ changelog:
Restored the following missing apps:
EmailWidget.apk added
LiveWallpapers.apk added
PicoTts.apk added
SamsungWidget_News.apk added
SamsungWidget_WeatherClock.apk added
SecretWallpaper1.apk
SecretWallpaper2.apk
ShareApp.apk
Swype.apk
Tasks.apk
Added k0nane's NO-CIQ mod
Orange Overscroll Glow (result of the NoCIQ mod)
Added Chris41g's kernel found here
Deodex WITHOUT NO-CIQ mod
Restored the following apks:
EmailWidget.apk added
LiveWallpapers.apk added
PicoTts.apk added
SamsungWidget_News.apk added
SamsungWidget_WeatherClock.apk added
SecretWallpaper1.apk
SecretWallpaper2.apk
ShareApp.apk
Swype.apk
Tasks.apk
Added Chris41g's kernel found here
Odex changelog:
Added Chris41g's kernel found here
Changelog 10/1/2011
Roms were compiled from odex and deodex system dumps
Modified cnz's updater script to fit these roms
Inserted Bubby's Stock Kernel zImage w/ ClockworkMod 4.x
How to flash if I am not rooted stock?
Hi can you provide a just a few more steps for people like me who are still on stock non rooted rom? I know it says save it on and then flash.
Welcome to the party!
Samsung Galaxy S II
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
spdwiz18 said:
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
+1
Sent from my SPH-D710 using Tapatalk
spdwiz18 said:
Thank you for you hard work And i totally agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kernel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
From my understanding the kernel is built from stock source not the sgs2. However, the cwm is built using the sgs2 binaries to save time. I know a new version is being worked on. I have been using Bubby's stock cwm for about a week and it is working great. Using a jig removed the exclamation mark and the i9100 screen so I am happy where I am. But I am looking forward to a new release that is completely stock with hopefully nothing but boot animation support and init.d. I hate having root and busybox built into the kernel. Just a personal issue.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
Great work absolutezerogi!
CWM first?
Do I need to flash CWM first for this to work? In that case which CWM should I use? I see two versions available.
Thanks.
rukshmani said:
Do I need to flash CWM first for this to work? In that case which CWM should I use? I see two versions available.
Thanks.
Click to expand...
Click to collapse
Yes. I use Bubby's.
Looking for something Stable... Hope I find it here ( ACS are normally stable ) giving it a shot now! Thanks
So far, this seems to be the closest we can get, without actually getting there.
I have tried Zedomax, and had a few LOS', no big deal, but I went back to stock.
If I go back to Zedomax (CWM, SuperUser, Root), can I flash this in CWM and have a completely stock rom with CWM, SuperUser, and Root WITH the stock kernel?
Thanks in advance.
spdwiz18 said:
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
Got your developers backwards lol. Zedomax's first kernel was from source and initramfs from the SGSII international. I pulled the initframfs myself for bubby's kernel, it's stock I promise
Hi can you provide a just a few more steps for people like me who are still on stock non rooted rom? I know it says save it on and then flash.
Click to expand...
Click to collapse
Hi there!
First you must be rooted. If you're not you need to go to one of our root methods and get rooted and get recovery. Then you just flash these in recovery However, I will make the instructions a little more detailed for ya.
Hi guys!
UPDATE: Now includes busybox.
Enjoy!!
Off topic, but do you suppose cm7 will be compiled using this kernel?
Sent from my SPH-D710 using XDA App
asafegous said:
Off topic, but do you suppose cm7 will be compiled using this kernel?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This is stock rom with TouchWiz and Bubby's completely stock rooted kernel. CM is made fro AOSP (Android Open Source Project) source and then ported to a phone. So, CM won't be using this at all lol.
crap!
UPDATE 2 - back in business. needed to flash stock kernel/rom then let it encrypt, then tell it to decrypt, then re-root, re-flash, back to normal again.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Downloading this as soon as I can. Thanks for your hard work!
Sent from my Galaxy S II
realmrealm said:
UPDATE - So I've been able to get the phone to mount to the computer, but I'm stuck in a loop at this Sprint 4G animation. It just keeps playing it over and over again. (5 minutes now) - I'm just going to let it keep going and see what happens.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Click to expand...
Click to collapse
odin zedos v3 to get cwm then flash this to get back where you want, pm me if you need help.
op, great work on this sir.
realmrealm said:
UPDATE - So I've been able to get the phone to mount to the computer, but I'm stuck in a loop at this Sprint 4G animation. It just keeps playing it over and over again. (5 minutes now) - I'm just going to let it keep going and see what happens.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Click to expand...
Click to collapse
I'm also going to PM with these instructions so I can be sure they get to you faster.
Go here: http://forum.xda-developers.com/showthread.php?t=1282420
download the stock tarball made by crawrj
boot into download mode (volume down + power)
Odin that tar. It'll return you to pure stock (unrooted, stock everything). You should be able to boot then. Do a factory reset once you do (to wipe everything), then you should have a functioning phone to re-root and do whatcha want. Let me know if that works.
Thank you so much OP. I flashed to v4 of Zedomax, then I flashed your ROM in CWM, and now I have everything. CWM, SuperUser, and all of my root apps are working on a deodexed ROM!!!
Thanks again.
Sent from my Galaxy S II
Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App
NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.
Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked
Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.
This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.
Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.
I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.
Here is my situation:
Galaxy S2X (telus) on wind mobile
1) successfully updated to ics via kies
2) followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1703045
FLASH ONLY USING - ClockworkMod Recovery 5.0.2.7 - NON Touch Recovery
01. Download ROM (Link is Below)
02. BACKUP ALL APPS with preferred method (ie: Rom Toolbox, Titanium, My Backup, etc..)
03. Place ROM on ROOT of your SD card. (ie: /sdcard)
04. Boot into Recovery Mode
05. Do a NAND BACKUP!!!
06. Flash DARKSIDE.SUPER.WIPE (OPTIONAL - ROM will do this by default)
07. Flash an ICS ready radio (Links below)
08. Flash ROM.
09. After flashing is complete, Reboot...
10. Let device sit for 10min without touching, then reboot.
11. Done!
Radio installed with error but i continued anyways. I was able to flash the rom and reboot without any issues but the gps reception is really bad. Takes over a min sometimes to lock on.
So i'm wondering if it's the radio and if it's okay to re flash just the radio using cwm.
Is step 3 important? can i have the roms in a separate folder and just navigate to it in cwm to flash it?
thx
Remember if you are using any Darkside ROM apart from Beta 3 I believe, it will have GPS problems. Also use one of his modified radios. Use the lastest Official Modified kernel.
alphadog32 said:
Remember if you are using any Darkside ROM apart from Beta 3 I believe, it will have GPS problems. Also use one of his modified radios. Use the lastest Official Modified kernel.
Click to expand...
Click to collapse
agps fix from dev section fixes GPS issues
Sent from my SGH-T989 using XDA App
Hexkode said:
Here is my situation:
So i'm wondering if it's the radio and if it's okay to re flash just the radio using cwm.
Is step 3 important? can i have the roms in a separate folder and just navigate to it in cwm to flash it?
thx
Click to expand...
Click to collapse
Yes you can just reflash the radio. Did that myself and no issues. Just make sure you check the MD5 sum of the zip file to make sure there's no corruption.
Step 3 is optional; you can always just navigate to the file in CWM.
http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
sewer56lol said:
http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
Click to expand...
Click to collapse
Hi , what was your rom before trying to install miui?
It seems so I had two recoveries at that point of which one being the leftover and which is terminated upon forst boot and one in the IcsBeta Kernel. What have I done is used the leftover CWM and that was the error. Anyway I found out this by accident when trying to enter flashmode and I didn't realise the kernel booted. I've flashed this rom using the kernel's touchscreen recovery and that worked for me. Anyway to answer your question it was 2.3.4 stock (.58) Enhanced version v2 anyway considering this is as an ICS ROM I should be able to get to it with any Gingerbread version.
Sent from my R800i using xda app-developers app and Miui v4 - Which IS installed.