Database Users

FYI: OTA URL capture

I don't know how useful this will be, since many of the devs have probably gleefully pounced on the 2.1 leak (and can't roll back now to Cupcake), but...
The OTA update process (1.16.605.1 -> 1.17.605.1) is completely different than the RUU/HBOOT methods... it actually boots into android and performs file-by-file binary patching on all sorts of stuff as well as installing new files and other miscellany - controlled by an "update-script" (not a shell script, but quite readable).
The OTA .zip files which are downloaded from a Google server are not signed the same way as the RUU "rom.zip" files - they use the app .apk manifest signing method. (manifests and certs a la "jarsigner").
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Note: because the 2.1 release is so vastly different than the 1.5 release, an OTA (if that's the way VZW/HTC rolls it out) for that will probably be very different than a patch release like this example ... but it would still be very useful for anyone who gets notice of an update to capture the URL using the "logcat" method shown above. There might be "interesting" tools included that could be exploited.
I don't think this will help get an "early OTA" - I'm not sure that hboot/fastboot methods can make use of an "update.zip" with an unrooted phone. Someone can correct me if I am wrong about that.
bftb0

Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.

pharaohmd said:
Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.
Click to expand...
Click to collapse
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.

nindoja said:
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.
Click to expand...
Click to collapse
Thanks...thought so but wanted to check...I tried to search but there have been so many */*/*/etc posts it's a bit confusing.
(edited out the example search terms so as NOT to contribute to the mess with this post...)

can sombody do this with the Update that just started pushing tonight?

iornslave said:
can sombody do this with the Update that just started pushing tonight?
Click to expand...
Click to collapse
Since so many of the XDA members are rooted, we're going to have to count on one of the "leakers" to capture it. We've confirmed (on android forums dot com) that it's coming to those on leak v3, which makes sense since that's up-to-date with the RUU and OTA.

No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.

hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I'm sort of wondering if VZW had some customer problems with it and pulled the plug on it. In the past, there have been claims that VZW starts the rollout in very small groups - several hundred at a time - and then ramp it up if they don't see complaints coming in from their customer support channels.
Sure does seem like there's very little chatter about it.
I've got my phone running OTA-2.1 to try and intercept it, and I also hacked a custom recovery that doesn't automatically erase files in /cache (basically, a recovery boot that doesn't run /sbin/recovery at all). That way I can just pull it out of /cache as soon as it is downloaded via OTA.
Nevertheless - to anybody reading this - please post up the URL to the zip file download if you capture it.
bftb0
[Edit] For references, PRIOR OTA URLs were
1.17.605.1 (aka "MR2") OTA: https://android.clients.google.com/packages/desirec/desirec-ota-104882.7b1e5cca.zip ( md5sum: f6bd240c726874e3922767979ecc6b32 )
2.36.605.1 (aka "OTA-2.1") OTA: https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip ( md5sum: 9a3a82e4b5afb4e885b41d28085b9adc )
Note: both these links verified working w/ correct checksums as of 2010-07-01.

hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I agree I have been hoping someone would have posted it considering that several have claimed to have received it. Oh well, hopefully soon.

Maybe all the people who are "smart" enough to do this are already rooted?

Stonent said:
Maybe all the people who are "smart" enough to do this are already rooted?
Click to expand...
Click to collapse
Nothing about root prevents you from running a copy of OTA2.1 for a couple of days in order to capture the URL; that's what Nandroid backups are good for. S'pose you could run Plain Jane or Ivanmmj's Official and add back in the updater apps & certs if you really needed root in the meantime.
OTOH, it's been mighty quiet the past few days; I'm starting to wonder if there was a problem with the new OTA, and VZW pulled the plug on it.
bftb0

[ROM] Acer_A500 OTA 7.014.14 [HC 3.2.1] Rooted w/ Busybox for CWM [Jan 6th, 2012] EOL

ROM: (HonnyComb)
Here is an ACER 3.2.1 near stock android image installable via clockwork recovery.
(Tested on a Wifi only acer a500)
[size=+2]acer7.014.14_CUST_ROOT_BBv4_S.zip[/size]
(MD5: cfd6ecee33891cc8e6e2625e8ea89511)
Note: April 30, 2012: The stock kernel will work both on HoneyComb and unlocked (v3) ICS bootloaders
Note: May 18, 2012: The update, no wipe required, to this ICS rom is now posted here this thread will remain for anyone remaining on HC​
Simply install via clockwork or RA recovery; if you have a rooted and mostly unmodified version of HC 3.1/3.2 currently it may be possible to use this install without a wipe (4.010.41 users are likely to have the best results); However make sure you backup first just in case.
Users of the previous (acer7.006.01_CUST_ROOT_BBv2) version may safely upgrade without a wipe however the following is recommended: 1) wipe dalvik cache in the advance menu of CWM recovery, 2) you may need to the apps menu to get the new market icon (my previous homescreen shortcut was no longer valid but the one in the app list worked without a problem, as making a new shortcut)
Last if you notice slowdowns or forcequits withing 24/48h of upgrading before reporting them try going into recovery and running both "fix permissions" and "clear dalvik cache" then boot the tablet waiting for the logon screen to appear and the screen to dim and turn off before using the tablet. At this point you van use the tablet normally.
This file is based off the OTA update: Acer_A500_4.010.41_7.006.01_COM_GEN1_1315966386585_07733ac7.zip subequently updated to 7.014.14_COM_GEN1 by manually extracted these images
(As was sent via OTA here in canada)
Modification Log:
I've made the following changes to the original OTA files:
decrypted and configured for installation from clockwork recovery
remove the bootloader flash (Separate analysis will be required to tell if this is safe) If so it is still not useful in a rooted Clockwork rom install, since in future it may become a downgrade not an update.
remove recovery flasher
remove both OTA cert and original ca_certs in favor of the cacert by guardianproject
Add a version of busybox (built in my HTC Dream rom ezGingerbread build tree using target utility_busybox from the commit https://github.com/CyanogenMod/android_external_busybox/tree/995d0d35bde285)
make busybox the default shell
Include Superuser/su
configure runparts (runs scripts in /system/etc/init.d) only a "Welcome" script is included however if you wish to run any script on startup you can do so by adding them to your /system/etc/init.d directory)
Note this rom is still odexed
(v2) fix she-bang on am, bmgr, ime, input, monkey, pm, svc shell scripts
(v3) incorporate "Skype Fix" into rom, thus no need to flash a second file to fix skype video calls (obviously you still need to install skype from market)
(v3) incorporate "wifi fix" for infinate DHCP leases, unfortinatly this was still not working in the base rom, however the fix is now part of this install.
(v3) uninstall Future Dial (acer updater) this prevents the system update from appearing in the menu/background, as it won't work anyway with the modificaitons
(v3) rebased to Acer A500 7.014.14_COM_GEN1 (previously 7.006.01_COM_GEN1)
(v3) SuperUser updated to v3.0.7
(v3) Set wifi only by default (if you need otherwise you will need to comment out the last line of the build.prop file, information in the comment above said line)
(v4) Remove extra market related files (merge errors from the acer patches); this ensures the new version of market runs properly (thanks to civato for pointing this out)
* entries starting with (vN) - indicates fixed/added in version N, ie (v2) indicates fixed in version 2 and on
Additional Information:
This is a very simple set of changes that ought to allow rooted users looking for a basic version of Honeycomb 3.2 (and now 3.2.1) safely update without loosing root. Its intended for users that wish a minimally modified rom with root. Either to be used as a rooted stock rom as is; or to be a base to make other small modifications as needed.
As such I'm more likely to provide addons than changing the base rom its self. (excluding any bugs of my creation or new official releases form ACER)
Note the kernel is the stock kernel from acer. Acer's A500 kernel source code can be found at here
FYI: You may use this as a base for other roms as long as credit is given with a link back to this thread where reasonable.

Add Ons
~~-- Stock Kernel Modules --~~
Here are some kernel modules for the stock acer kernel
(Tested both on acer7.006.01_CUST_ROOT_BBv2_S, and acer7.014.14_CUST_ROOT_BBv3/acer7.014.14_CUST_ROOT_BBv4)
tun.ko
md5: bf93f2538c875f0f397f43f225bd595b
cifs.ko
md5: 86b936fb269daa1f688f3f8535c36c23
Since I'm having problems with a corrupt tar.gz file with the latest posted [by acer0] a500 kernel code; these have been built from the a501 version with a a500 config. (the "Application Guide (for Android 3.2 HoneyComb" posted on 9/19) Hopefully this will not be an issue but let me know if you have any issues with the modules (I've checked they load but not that they are fully functional)
~~-- Villain Iconia Kernel --~~
(Tested both on acer7.006.01_CUST_ROOT_BBv2_S, and acer7.014.14_CUST_ROOT_BBv3/acer7.014.14_CUST_ROOT_BBv4)
Here is a re-bundle of the Villain Iconia kernel (original zImage form richardtrip) The installer however has been modified since we now need a new ramdisk image than the one previously bundled with the kernel.
V3.7
acer7.006.01_CUST_ROOT_BB_Villain_iconia_kernel_3.7_S.zip
md5: 57908bd9d8fda3902cc24ebb23de9e6c
Previous verison:
acer7.006.01_CUST_ROOT_BB_Villain_iconia_kernel_3.4_S.zip (md5: 8c6c0783a961d65d465a3f3dccffbfb3)
For more information including source code see Villain_iconia_kernel_3.4.zip from Stock/HV/Taboonay V3.4 for HC 3.2 10-09 - 1.64Ghz/UV control
(This will let you overclock and access some more modules, but I've found the stock kernel overall more stable)
--------------------------------------------------------------------------------------------------------------------------------------
[Size=+1] The following is only for the previous acer7.006.01_CUST_ROOT_BBv2_S version:[/Size]
---------------------------------------------------------------------------------------------------------------------------------------
~~-- Wifi Dropouts Patch --~~
If you are having issues with your wifi connections it is recommended to check your router doesn’t have indefinite DHCP leases
However if you can't prevent the indefinite lease a patch for such dhcp connectivity problems is available:
wifipatch_7.006.01v2_S.zip
MD5: 39c0a1cdd755458eb6edd6aa786e4f5f
Additional details here
(Note this have been built in on V3 and thus is no longer needed)
~~-- Skype(tm) Patch --~~
Fixes video calls on market skype client
skypepatch_7.006.01v2_S.zip
MD5: 99cadf8c5b8eca25aa60b38aa83ec91a
Flash from recovery; and install skype form market as usual (or open it if already installed) video options will appear in settings.
Details of the problem/solution and the patch are in this post
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- Netflix --~~
Install from market:
https://market.android.com/details?id=com.netflix.mediaclient&feature=search_result
If you previously installed a modified version such as the one modified to play on the a500 without breaking video you will need to uninstall the modified version prior to installing the market version.
~~-- Cell Standby fix/option --~~
If you are seeing Cell standby in your battery use simply add ro.carrier=wifi-only to your build.prop
Via adb:
Code:
adb remount
adb shell
echo 'ro.carrier=wifi-only' >> /system/build.prop
sync
reboot
Via terminal/local connectbot
Code:
su
mount -o remount,rw /system
echo 'ro.carrier=wifi-only' >> /system/build.prop
sync
reboot
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- SuperUser 3.0 update --~~
We need to flash the rom manager update, but as rom manager is not yet working on this tab get the update zip and flash in recovery:
su-3.0-efgh-signed.zip
Md5: c05902fdf90f7635c711e4dcd1c32c45
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- Previous Versions --~~
[size=+1]v1: acer7.006.01_CUST_ROOT_BBv1_S.zip[/size]
(MD5: df11f6a309f34ac4c0209aded4ca3f20)
This version had an error in the she-bang of the included scripts such as pm, v2 corrected this to the expected '#!/system/bin/sh'
To save bandwidth I'm not providing the original file; however you can re-generate it with the following binary diff:
On a linux computer with the bsdiff package installed run:
Code:
bspatch acer7.006.01_CUST_ROOT_BBv2_S.zip acer7.006.01_CUST_ROOT_BBv1_S.zip acer7.006.01_CUST_ROOT_BBv2_to_v1.bsdiff
Using the v2 version and acer7.006.01_CUST_ROOT_BBv2_to_v1.bsdiff
[size=+1]v2: acer7.006.01_CUST_ROOT_BBv2_S.zip[/size]
MD5: b254140896742f3deec464c094fb2515
Longtime running version very stable, however some users have had some minor issues correctable by the above patches.
[size=+1]v3: acer7.014.14_CUST_ROOT_BBv3_S.zip
[/size]
MD5: c734317089d323dffde9c7d4fe7afce4
Inital upgrade to 7.014.14 had some issues with extra market related files, if you are running this version it is recommended to upgrade to V4 or (if you wish to avoid the download and the cost to me of the bandwidth) follow the instructions here to manually make the same change yourself.

Does Netflix work or do you still have to use a patch
Sent from my Nexus S 4G using XDA App

ruffjd said:
Does Netflix work or do you still have to use a patch
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I still needed the patch (you will need to apply it by hand)
I hear rumor's [but have not spotted it first hand] of some library that works with both camera and the library.. if I find that one I'd be happy to make a flash-able patch.
Also looking at the Stock/HV/Taboonay kernels, since he is not extracting the ramdisk from the existing boot.img it looks like they will not be 100% compatible with this rom out of the box. (will make something up shortly)
10/2: see note one netflix

Thanks, Working Great
I flashed from 4.010.13 without a full wipe without any issues. I cleared cache, wiped dalvik cache, and flashed. Thanks for your work. This ROM will be very useful for those of us that want to retain root and take advantage of the stability that the stock ROM brings.

Small bug with shell scripts such as pm, This can cause problems with rooted applications expecting them or adb commands, to fix just grab the updated version at the top of the op acer7.006.01_CUST_ROOT_BBv2_S.zip
If you already updated you can safely flash this new version over your current one; however if you subsequently changed items in /system (such as the netflix hack) you will need to make the change again after the upgrade.
Apologies for missing this in my initial testing last night. (my fault for working on this practically while sleeping..)

.. and A501 3G

why is it that when scrolling apps or scrolling of the home screen became sluggish after installing 3.2?

superbar said:
why is it that when scrolling apps or scrolling of the home screen became sluggish after installing 3.2?
Click to expand...
Click to collapse
If you had a non stock rom ported from another device it could be just incompatible data and a wipe is needed.
If it was a stock rom it could be a data issue try wiping dalvik cache and running fix permissions in recovery.
It could also be something ypu have installed. (Widgets in particular)
I see no slowdown really I don't see much difference from a user perspective from 3.1.
Börger said:
.. and A501 3G
Click to expand...
Click to collapse
This is a a500 stock rom with root modifications..If it works on a a501 great.. but if not I can't support it.. its another device.. Likely 3g will fail.
If works or you have a patch for me to make it work feel free to let me know however.

I wondered how you got the OTA when you have A500_4.010.41 originally ??
I thought North America the latest HC3.1 was version A500_4.010.13_COM_GEN2 ??
anyway...
I am on A500_4.010.13_COM_GEN2 rooted with CWM... should I go ahead and flash this ??
I understand that it will keep root... and since I will have root... I guess I can use "Acer Recovery Installer" to re-install CWM ??
and freaking Acer !!!... we were on GEN_1 originally awhile back (HC3.0.1)... then went on to GEN_2 (HC3.1)... now with HC3.2 they are back with GEN_1 ??... freaking confusing idiots !!
and the A501 is keeping this format (4.015.01)...similar to HC3.1 format !
while us A500 is going to this format (7.006.01)
Side note:
If we are seeing custom roms for HC3.2 keeping root..etc... why can't dev managed to root stock 3.2 ??
and is the CWM recovery working for 3.2 ??

UnicornKaz said:
I wondered how you got the OTA when you have A500_4.010.41 originally ??
I thought North America the latest HC3.1 was version A500_4.010.13_COM_GEN2 ??
Click to expand...
Click to collapse
No clue was what the device auto updated to what I had, then I rooted (+ intercepted the OTA last night).. I don't know the regions ACER is using.. butthe tab was purchaced at a local staples.
UnicornKaz said:
I understand that it will keep root... and since I will have root... I guess I can use "Acer Recovery Installer" to re-install CWM ??
Click to expand...
Click to collapse
The update I've provided won't touchrecovery, so you keep your current recovery and thus can restore your backup even if you mess up the rom.
You also will have root so you can re-flash reocvery if something goes wrong. But likely won't need to.
Last I'm not touching the bootloader so that will also remain as is.
UnicornKaz said:
Side note:
If we are seeing custom roms for HC3.2 keeping root..etc... why can't dev managed to root stock 3.2 ??
and is the CWM recovery working for 3.2 ??
Click to expand...
Click to collapse
Keeping root is diffrent from rooting the new system:
To keep root I pull the update zip from the system without letting it install, then I decrypt it (since acer encodes it) unzip it, then manually add/remove files to the update zip before installing via clockwork.
This way I don't need root to install superuser/su on a locked down system, but just install it via clockwork with the correct permissions.
Also recovery is seperate from the andoid system (seperate linuxkernel/ram disk from the main boot kernel/ramdisk) We need not touch it when installing a rom (even if most stock roms by default like to reflash recovery.)

I flashed my Packard bell libertytab with this rom and everything is just fine.
CWM and root.
Thanks.
Edit: I got the Thor 3.4 kernel running on it and it is fast.
24/7 at 1544MHz and even 1680 is no problem with it.
Max cfbench overall score is 9175.

my only problem is that the OP doesnt sound too sure of himself if this rom is even any good
thats just the feeling i got after reading his first post
it almost sounds like you dont have an iconia to test this on.
i do hope i am wrong. i guess i have not seen anyone post a rom and use the words in the manor you have. it just made me feel uneasy about if the rom even works.
Sent from my A500 using Tapatalk

v_lestat said:
my only problem is that the OP doesnt sound too sure of himself if this rom is even any good
thats just the feeling i got after reading his first post
it almost sounds like you dont have an iconia to test this on.
i do hope i am wrong. i guess i have not seen anyone post a rom and use the words in the manor you have. it just made me feel uneasy about if the rom even works.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I have an icona.. and its running the rom.
But the OTA hasn't even been out 24h (rooted or otherwise) so I've not had the time to really put the rom into its paces (nor has anyone else not working at ACER)
The other thing is my position on this rom; That is unless there is (a) a bug in the modifications I did make to provide root and some tools for end users to add their own tweaks; or (b) another official release provided by acer: I do not want to be updating the base rom; it ought to remain nearly as close to the stock OTA as possible (and any exception to this is already defined in my modification list)
Now if you have a interesting addition.. Or I come up with an interesting hack I'm happy to provide/advertise it as an "Add on" that the user may optionally flash on top of the rom to obtain the additional functionality.
(Of course I much rather work on roms with accessible source code.. unfortunately we will not be able to make such a thing until Google releases the source for Ice Cream Sandwich)

Rom appears to work fine fine. Cleared cache and dalvik cache and flashed to my Iconia with CWM from stock 3.1 and voila - 3.2
Flashed the modified HoneyVillain Kernel in post 2 and overclocked to 1504. Everything working fine so far. Netflix working with patch (rear videocam FC as usual).
I'm hoping for better battery life than Taboonay. Maybe it was just me, but I had awful battery life with Taboonay compared to stock.
Bob
---------- Post added at 05:12 PM ---------- Previous post was at 04:44 PM ----------
I should mention after flashing that kernel I put ro.carrier=wifi-only into /system/build.prop to remove cell standby from battery use.
Also, since I didn't do full wipe, this truly came out as an upgrade, since everything on my tablet stayed the sam ein terms of apps and configuration

Scrolling thu home screen is smooth now but scrolling thru apps still lags, not as smooth as 3.1, I wipe my dalvik cache and clean wipe, should I wipe my partition?

As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.

He already explained a few posts before. He took the update, dismantled it and took out the bit that will upgrade your recovery and wipe out the root. Repackaged it and viola! instant magic!
HarshReality said:
As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.
Click to expand...
Click to collapse

HarshReality said:
As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.
Click to expand...
Click to collapse
Most of the "tweaks" in here are you find not as optional as you may think.. Particularly for a distributed product.
However I've not modified any binary files; this means all the changes are either text files or removal/addition of binary blobs thus to see what I've done:
You need the official OTA image and to decrypt it/unzip it information is here:
http://forum.xda-developers.com/showthread.php?t=1113878
(As well on two 3.2 update related threads happening in the a500 dev section)
Once you have unziped the zipfile and update.zip will be visible and is the base of the update.zip for this install.
In that file is system files, recovery flasher files a boot.img (this contains the ramdisk where I have modifications so adb shell works as root look into extracting the ramdisk with cpio) and scripts to help in the installation of the rom.. the updater-script (a few dirs under META-INI) is the script recovery runs.
From here you can compare the files in the official archive with mine, or ignore mine and modify the install to your own liking.
For best results knowing the structure of the files in system and how linux/android boots is important. Otherwise this is a hands on exercise, there is only so much advice I can give,thus looking at the original and seeing what I touched will likely provide insight particularly if your are stuck.
In the case of su/superuser I just pulled from the official zip on rom manager provided by ChainsDD (links at https://github.com/ChainsDD/Superuser/blob/gh-pages/manifest.js ) and placed them into system making sure to add the suid perm on su in the updater-script. This however will not allow adb shell as root or prevent clockwork recovery from being over written.
There is a bit of a learning curve.. even if to me this type of hack is trivial and I only bothered doing it so I could have the 3.2 OTA without loosing root, and without what I think are silly tweaks some other devs add.
suomaf said:
He already explained a few posts before. He took the update, dismantled it and took out the bit that will upgrade your recovery and wipe out the root. Repackaged it and viola! instant magic!
Click to expand...
Click to collapse
Not very technical.. but once you decide to use the rom yes is about how its supposed to act.. And how I hope most of those that have downloaded the image think of it.

When i flash this, and reboot, i hang on the Acer bootup logo. No changes. I can go back into recovery and restore, but i can seem to get this to flash properly. I'd like to have a nice clean minimal 3.2.
I even wiped and did a clean instal, one note it did say
Offset:0x180
Before it said installation complete, it also 'installed' the file far to quickly in my opinion.

[REF] Nexus S ROM&Kernel Survival Guide

Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs​(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]

Kernels​
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]

Tools & Mods​
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)​

Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk

ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

nice thread! thanks

Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!

Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..

Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.

Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App

Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.

very useful for us newbie, thanks for sharing

heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...

great post OP

Nice thread! Great Work ,Thanks

Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI

Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse

You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht

[ROM - 1.2] BETA ICS 4.0.X - Team DRH (Update 07/02/12)

CLICK PIC FOR TEAM HOMEPAGE​
Now for the moment you all have been waiting for...
Team DRH (Dirty Reset Hole) is proud to announce the public beta for Ice Cream Sandwich. The name "DRH" came from the hole that all of the developers had to drill into the back of their tablet to access the on-board reset button. As you all probably know, development for this project started back in August and has finally developed into a mostly stable release. Ice Cream Sandwich is a huge jump for the G-Tablet community because along with the building of ICS specifically for SMBA1002 (G-Tablet), the Linux kernel backbone had to be reworked from the ground up.
DISCLAIMER
Attention commuters of the intertubes! The group of individuals known as Team DRH take absolutely NO RESPONSIBILITY for any DAMAGE that YOU cause to YOUR device! This "labor of love" we call and Android ROM comes AS IS and is not an official release by any means. If you have not already SOILED your device by flashing a custom ROM then to do so will VOID any WARRANTY you may have left. Team DRH and its affiliates are not responsible if your G-Tablet does any of the following: Explodes, Flies off to space to battle the Flying Spaghetti Monster, Is generally awesome, solves world hunger or explodes... again. (OK We take responsibility for you Tablet becoming Awesomesauce.) So in essence... Flash this totally rad ROM at your own RISK and prepare to Spontaneously Combust with AWESOMENESS!
WHAT WORKS
WIFI
Hardware Acceleration
Sleep!
WiFi
Bluetooth
Sensors
Sound
USB/MTP (If you plug in USB while your tablet is asleep you will have a SOD)
Capacitive Buttons
Hardware Buttons
USB Flash Drives
Proper SD Card Mounts
HD Videos
More to come...
WHAT'S NOT WORKING
Camera
Microphone (Works but drops after 6-8secs)
Possible ROM Slowdowns
HDMI Audio
More to come...
List of Common ICS Problems
http://forum.xda-developers.com/showthread.php?p=23146434
HOW TO INSTALL
Boot into current version of CWM and "Wipe data/factory reset"
Partition Internal SD Card (2048M/0)
Turn tablet off
Download the following file <--- Seriously don't skip this step unless you are 100% positive that you have a 250M system partition
NVFLASH the file following the instructions that are included for Windows/Linux users
Upon reboot of tablet let T&T fully boot and then shut it down
Reboot into recovery
Flash the Rom/Gapps
Enjoy
HOW TO INSTALL VIA DRH NEWS APP
1. Open DRH News App (You Will be notified that you have an update)
2. Download Update
3: Reboot into CWM
4: Wipe Data and Cache
5: Flash Update.zip
6: Flash Your Gapps
7: Reboot
8: Enjoy
FINAL THOUGHTS
This build has been tested but not to the extreme. It is called a "beta" test for a reason. Sleep is properly working and I have not had to use my reset button in weeks. I'm not trying to scare anyone but the possibility of a kernel panic is still there. This build is very stable and deserves the beta tag but if you find yourself in a snag you might have to press the internal reset button. Here is a picture of where to find the button if you are really in a bind. PICTURE If you have the balls to open your tablet, just drill the reset hole while you're in there. You already voided your warranty
DOWNLOAD LINK
ROM/GAPPZ Package: TeamDRH ROM
ROM (Includes GPS Mod): TeamDRH GPS ROM <-- Only use if you physically installed the internal GPS mod as documented here. This rom is not updated to 1.3 yet.
Remember this is a beta build. It will run nicely for the most part but I'm sure that there will be glitches a quarks that we have not seen. I will keep the what works/doesn't work section updated so we don't have tons of posts cluttering the thread. Also these links will be updated pretty regularly when we have new builds to release.
CHANGE-LOG
The ROM's system folder was very close to the max size our system partition could handle on the G-Tablet and with any bad blocks, it was more than the G-Tablet could handle and installing GApps made it even worse. So on initial boot everything was fine, because all the apps that make temporary files don't make them until after initial boot, but in the process of making those temp files it corrupts system files that are already loaded and running, so on a reboot the system fails because the files are now corrupted. This also effected the overall speed of the ROM. This should be fixed with the increased system partition from 200M to 250M.
TeamDRH-ICS-Beta-1.3.zip 07/02/12
Kernel changes to help stability
Wifi Updates (latest bcmdhd android code)
Changes to sound (should reduce audio lag)
Mic Partially Working (Will record for roughly 6 - 8 seconds)
Dock Support with HDMI and Ethernet (No Sound over HDMI yet) This includes a dock clock mode
"Blinkies" Have been fixed
Updates to CM9 code. Now includes lots of the CM9 features
Overall stability improvement
New Boot Animation
Added Sound to Boot Animation (Optional)
New Default Wallpaper (created by annel)
Installer Updated
Gappz Changes
Updated Google Plus
Updated Google Books
Updated Google Chrome Browser
YouTube Updated
Google Drive Updated
Google Play Updated
Google Currents Updated
Added Google Magazines (From JellyBean)
Added Google Ears (From JellyBean)
Probably more changes too this is just all I could remember
HOW TO INSTALL MTP DRIVERS
Open Device Manager and find the offending TeamDRH MTP device.
Right-Click and choose Update Driver Software
Then choose Browse My Computer for Driver Software
Then click Let Me Pick From a List of Device Drivers on My Computer
Then choose All Devices
When that list populates choose Standard MTP Device followed by MTP USB Device
Click Yes to the warning and VIOLA!
Hope you all enjoy the TeamDRH gTablet ICS preview!!
POSSIBLE MARKET ERROR
Upon start up Android Market may give you an error when you try to download an app. The fix for this is to go into settings/applications and force close market. Upon doing that clear app data and you should be good to go.
IF ALL ELSE FAILS (Only do this If I tell you too)
Try doing what is posted here
If you like this project and appreciate the extreme amount of time that the devs put into this please donate:
Donate to TeamDRH: LINK
If you would like to donate to single people:
Ch3vr0n5: LINK
Treznorx: LINK
Fosser2: LINK
The3dman: LINK
Plastikman: LINK
Mayday_jay: LINK
Dwagner:
Tlb1961: LINK
Busa_blade:
Jaybob413:
Clemsyn: LINK
(This is not a complete list yet changes are still being made)
Information on G-Tablet Camera!!!
http://www.slatedroid.com/topic/290...update-040112/page__view__findpost__p__346429
Video (courtesy of pagantek):
Pictures:

TeamDRH Change-log:
TeamDRH-AOSP-Preview-1e-LDPI.zip 02/08/12
USB/MTP
Vold.fstab
USB Flash Drives work if plugged in when tablet is off, then booted
SystemUI notification toggle bug
TeamDRH Welcome in Trebuchet
3g Icon
Few other little adjustments...
YAGP_GummyBear_Jay_GAppZ_v2.zip 02/08/12
Few extra added apps
Google Maps
Google Chrome Beta
TeamDRH-AOSP-Preview-1F-LDPI.zip 02/16/12
USB/MTP Now works even if plugged in on boot. If your tablet is asleep and you plug in USB your tablet will get SOD!!!
USB Flash Drives work should work if plugged whenever
New Touchscreen driver (should be more responsive)
New Battery Driver (should perform better. Has a charging icon issue.)
Capacitive keys should now fully work
Bluetooth now works
Few other little adjustments...
3DGtaB_GAppZ_v6b.zip 02/16/12
Few apps added/deleted
Tweaked Permissions
Should perform faster
TeamDRH-ICS-Preview-2A.zip 02/29/12
Added ROM control in settings.
Adjusted Dalvik Cache sizes for better performance (thanks community)
Much faster Read/write speeds (probably better than Froyo)
Many i2c/clock changes to the kernel to improve stability
Amount of system ram increased from 295M to 359M!
Other various tweaks and speedups built into the ROM
Games should play better in this release
3DGtaB_GAppZ_v6c.zip 02/29/12
Few apps added/deleted
Tweaked Permissions
Should perform faster
TeamDRH-ICS-Preview-2B.zip 03/01/12
Moved some apps to the /data folder to reduce the size of the /system folder
New Boot Img - Fixes cache size
Added FakeIMEI to the framework so some apps that request one don't crash (ex. XDA App)
3DGtaB_GAppZ_v7A.zip 03/01/12
Moved some apps to the /data folder to reduce the size of the /system folder
3DGtaB_GAppZ_v7A_LiteEdition.zip 03/01/12
Added a new version of GAPPS
Very minimal app install (includes: Calender, Music, Youtube, Gmail, Gallery, Market)
3DGtaB_GAppZ_v7B.zip 03/17/12
Added new market/music Google play apps
3DGtaB_GAppZ_v7B_LiteEdition.zip 03/17/12
Updated Google applications
TeamDRH-ICS-Beta-1.0.zip 03/17/12
Changed ROM naming convention for future use
Overclocking (max 1.2GHz for now)
ROM is reworked and running on CM9 as a base
Noticeable speed improvements
250M system partition is a MUST now
Stability is improved
In-ROM battery stats should now be fixed for almost everyone
3DGtaB_GAppZ_v7B.zip 03/17/12
Added new market/music Google play apps
3DGtaB_GAppZ_v7B_LiteEdition.zip 03/17/12
Updated Google applications
3DGtaB-GAppZ-LiteEdition-8.0.zip 03/18/12
New DRH-News App
Added Play Store (Google Market)
3DGtaB_GAppZ_8.1.zip 04/01/12
Added Play Store (Google Market)
All Google applications are now updated and latest
TeamDRH-ICS-Beta-1.1.zip 04/01/12
Performance enhancements (based on some SuperCharger settings)
Kernel updated with new governors
Kernel updated with new i/o schedulers
Android updated to 4.0.4
Rom control has additional performance settings
3DGtaB-GAppZ-8.2.zip 04/07/12
Updated Gmail to 4.0.4
Update to Google Books
Fixed calender sync issues some people were having
Added the new installer that TeamDRH will now be using! (it's awesome!!!)
GAppZ full and lite will now be an all inclusive package. Just flash and follow the instructions.
TeamDRH-ICS-Beta-1.2.zip 04/21/12
ROM has been updated to include various performance tweaks
Kernel has added touchscreen fix (hopefully fixes most games)
Most i/o schedulers removed for now due to incorrect throttling
Rom control has additional performance settings and is reorganized
WIFI modules updated
Incorporated TeamDRH Aroma installer (now includes ROM and GAppz)
ROM does have issue where at times, will not go to sleep (screen will turn off then flash back on) aka "blinkies"

Wow I bought my Gtab Yesterday and this is the first thing I have tried... it is mind blowing !! If the Out-of-the-box feeling of this tab disgusted me to 50% this has excited me to 200%
Keep up the good work guys !!
Just one thing - the text on my gTab appears kind of blurry is it a resolution thing or is it because of the screen.
Overall superb !! Thanks a million for making my $275 INVESTMENT worth it !!
Some Donation Definitely Headed Your Way.!!

For those of you who are really struggling to install this build here is a (most likely) fail-safe method of getting it to work. It is lengthy and sucks, but is most likely worth it in the long run.
NVFLASH the following http://www.mediafire.com/?brd9u48iefdqcc7 Upon reboot, boot into recovery and partition sd card. 2048M/0M
Turn off tablet
NVFLASH the following (full 1.1 stock) http://www.mediafire.com/?48roksff1xji3y0
Fully boot into TnT (yes, you have to do this!)
Turn tablet off
NVFLASH this (full 1.2 stock) http://www.mediafire.com/?0rgkcd0k4v30z4u
Let TnT fully load yet again
Next NVFLASH TeamDRH recovery found here http://www.slatedroid.com/topic/28751-kernel-12-clockworkmod-5504-touch-recovery-team-drh/
Boot into recovery
Mount usb and delete all folders that were made from TnT. Then copy on ROM and Gapps.
Flash our current build of ICS (found in OP)
Cross fingers and hope it boots
The technical aspect behind this is supposedly TnT tags bad blocks in the nand and moves them. This method got me out of a nasty bootloop spree the other night, so it does work. If this works for you, let me know.

fosser2 said:
The technical aspect behind this is supposedly TnT somehow re-allocates bad blocks in your internal sd card.
Click to expand...
Click to collapse
Very unlikely.
The internal SD card is not a "raw" NAND device, so any bad block handling will be done, transparently, by the hardware. I doubt if TnT can get to that layer. In any case, most of those steps only touch the built-in 512MB NAND flash.

rajeevvp said:
Very unlikely.
The internal SD card is not a "raw" NAND device, so any bad block handling will be done, transparently, by the hardware. I doubt if TnT can get to that layer. In any case, most of those steps only touch the built-in 512MB NAND flash.
Click to expand...
Click to collapse
Could that re-allocate bad blocks in the NAND?

fosser2 said:
Could that re-allocate bad blocks in the NAND?
Click to expand...
Click to collapse
What kind of bad block? Factory-marked bad blocks on raw NAND devices are not reallocated. The filesystems (YAFFS2, JFFS, UBIFS) for these raw NAND/NOR MTD devices are designed to skip marked bad blocks. CWM and the utilities that come with it (dump_image, erase_image, flash_image) do this too.
BTW, fosser2, can you use the gtablet.cfg in this post instead of roebeet's version for people enlarging their system partition and installing the 1.2 bootloader.

rajeevvp said:
What kind of bad block? Factory-marked bad blocks on raw NAND devices are not reallocated. The filesystems (YAFFS2, JFFS, UBIFS) for these raw NAND/NOR MTD devices are designed to skip marked bad blocks. CWM and the utilities that come with it (dump_image, erase_image, flash_image) do this too.
BTW, fosser2, can you use the gtablet.cfg in this post instead of roebeet's version for people enlarging their system partition and installing the 1.2 bootloader.
Click to expand...
Click to collapse
For example these are the bad blocks I'm talking about:
Code:
<6>[ 3.334646] yaffs: dev is 32505859 name is "mtdblock3" rw
<6>[ 3.334798] yaffs: passed flags ""
<7>[ 3.334890] yaffs: Attempting MTD mount of 31.3,"mtdblock3"
<7>[ 3.441293] yaffs: block 1393 is bad
<7>[ 7.661086] yaffs: yaffs_read_super: is_checkpointed 0
<6>[ 7.661433] yaffs: dev is 32505860 name is "mtdblock4" rw
<6>[ 7.661520] yaffs: passed flags ""
<7>[ 7.661613] yaffs: Attempting MTD mount of 31.4,"mtdblock4"
<7>[ 7.733488] yaffs: block 1255 is bad
<7>[ 7.733613] yaffs: block 1256 is bad
<7>[ 8.188697] yaffs: yaffs_read_super: is_checkpointed 0
full dmesg here http://pastebin.com/tyPm3DpH
As for expanding the system partition: As far as I know, we aren't doing that. We are using "stock" values.

We have updated the ROM and GApps, be sure to check them out, the links are in the OP. The change log for the updates are listed here: Team DRH Changes

OP Updated again. New rom, minor changes.

Dammit now I have to check here and SD lol

i know your rom's not designed for Hannspad, but I have been flashing your roms, and they work fine, with our Hannspad kernel, though, with this latest version 2b, the wifi won't switch on, is this a known issue with all tablets on this rom? or is this somthing specific that has been introduced in this latest version, only effecting the Hannspad?
great work guys, keep it up.

I don't know much but I read lots
but I do believe they moved to bcmdhd 14 days ago which may not be supported in your kernel

serialplague said:
I don't know much but I read lots
but I do believe they moved to bcmdhd 14 days ago which may not be supported in your kernel
Click to expand...
Click to collapse
This is correct, and is the reason why it would not work.
Posted from my G-Tablet running Team DRH ICS

fosser2 said:
For example these are the bad blocks I'm talking about:
Click to expand...
Click to collapse
That looks to me like YAFFS2 doing its job.
As for expanding the system partition: As far as I know, we aren't doing that. We are using "stock" values.
Click to expand...
Click to collapse
Then the 2A ROM install with full Gapps v6c will overflow the system partition--one with or without bad blocks. I see from the changelogs that you've moved some of the apps from /system/app to /data/app in 2B, so now a 200MB stock system partition should suffice for the ROM proper.
There is another bad bug in both 2A and 2B, though. You're overriding the bootloader-supplied kernel command line with one in the boot.img. This is a very bad idea--see point 2 of this post where its caused problems before.
From your dmesg.txt (from a 2A ROM kernel?) on pastebin:
Code:
Kernel command line: [email protected] video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:[email protected][B]7424K(misc)[/B],[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected][B]24320K(bootbmp)[/B],[email protected](logodata)
The NAND partition assignment is pretty peculiar. On first glance it looks like the partition layout on my gTab which has a switched "misc" and "bootbmp" partition. However, most of the gTabs shipped by VS have their "bootbmp" first and "misc" next.
The boot.img in 2B is worse:
Code:
[email protected] video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:[email protected][B]7424K(misc)[/B],[email protected](recovery),[email protected](boot),[B][email protected](system)[/B],[B][email protected](cache)[/B],[email protected][B]24320K(bootbmp)[/B],[email protected](logodata)
In this both the partitions and the sizes are being overridden. It is, in fact, a very peculiar layout--a enlarged system partition along with the switched "misc" and "bootbmp". Somebody with the standard stock partition layout and sizes will eventually have problems when things get overwritten--their tablet might not even boot.
Seriously, Andrew, don't override the bootloader-supplied command line in this fashion.

rajeevvp,
You are right, we are over-riding the bootloader w/ our own command line. Without the change to the command line our system ram goes to 295M instead of 365M. That's a big change. We're working on fixing this issue right now and it will most likely be fixed in the next release.

As I am certain you must be aware, this effort is still a fairly early work in progress, but you may not know that there is additional effort underway to move to a more comprehensive set of changes regarding partitioning.
In the near term the intent would be to provide an updated nvflash configuration that would modify the partition table to expand system at the expense of cache. A similar approach (firerats) has been used for quite some time on other devices that are resource constrained like the G-Tab. This would entail a one-time nvflash that we are not quite ready to provide at this point.
The principle reason for this is that 200M is quite small to support newer software versions like ICS without requiring significant effort from a build/packaging perspective, that takes time and effort from the primary goal which is to deliver improved functionality to the end users.
Anyone who has performed an nvflash using either bekit or roebeet gtablet.cfg (likely a large portion of the community), already has a "non-standard" partition table (where system may already be closer to 250M than 200M), so while things like the misc/bootbmp swap may be different from the vendor standard, they are certainly not unique or even uncommon in the gtablet community that is not using tap'n'tap.
There is also really not much concern about whether the cache partition is large enough to hold an ota update from viewsonic, as that would certainly deliver significantly reduced functionality, and is precisely what most end-users are trying to get away from.
Of course, anyone that is not happy with the choices the developers make, can choose not to use it, and are certainly welcome to build their own rom and use partition sizes that they find more aesthetically pleasing.
Common courtesy might suggest that your ideas on how another developer's work should be modified would best be communicated via PM. This would provide the opportunity to understand the rationale behind certain decisions, rather than declaring them a "very bad idea" out of hand, or instructing them on how to proceed.
rajeevvp said:
That looks to me like YAFFS2 doing its job.
Then the 2A ROM install with full Gapps v6c will overflow the system partition--one with or without bad blocks. I see from the changelogs that you've moved some of the apps from /system/app to /data/app in 2B, so now a 200MB stock system partition should suffice for the ROM proper.
There is another bad bug in both 2A and 2B, though. You're overriding the bootloader-supplied kernel command line with one in the boot.img. This is a very bad idea--see point 2 of this post where its caused problems before.
From your dmesg.txt (from a 2A ROM kernel?) on pastebin:
Code:
Kernel command line: [email protected] video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:[email protected][B]7424K(misc)[/B],[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected][B]24320K(bootbmp)[/B],[email protected](logodata)
The NAND partition assignment is pretty peculiar. On first glance it looks like the partition layout on my gTab which has a switched "misc" and "bootbmp" partition. However, most of the gTabs shipped by VS have their "bootbmp" first and "misc" next.
The boot.img in 2B is worse:
Code:
[email protected] video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:[email protected][B]7424K(misc)[/B],[email protected](recovery),[email protected](boot),[B][email protected](system)[/B],[B][email protected](cache)[/B],[email protected][B]24320K(bootbmp)[/B],[email protected](logodata)
In this both the partitions and the sizes are being overridden. It is, in fact, a very peculiar layout--a enlarged system partition along with the switched "misc" and "bootbmp". Somebody with the standard stock partition layout and sizes will eventually have problems when things get overwritten--their tablet might not even boot.
Seriously, Andrew, don't override the bootloader-supplied command line in this fashion.
Click to expand...
Click to collapse

Wonderful, finally this has arrived here xD
Does the latest release fix TiBa bug in restoring?
Sent from my HD2 using Tapatalk

Abu-7abash said:
Wonderful, finally this has arrived here xD
Does the latest release fix TiBa bug in restoring?
Sent from my HD2 using Tapatalk
Click to expand...
Click to collapse
People have had success in restoring w/ TiBa. I guess you're gonna have to try it and let us know your experiences.

fosser2 said:
People have had success in restoring w/ TiBa. I guess you're gonna have to try it and let us know your experiences.
Click to expand...
Click to collapse
Glad to hear, been downloading it when I first saw it ut thought I ask and test so I would try even harder if it didn't work for me while being fixed.
Sent from my HD2 using Tapatalk

Cant Build for find 5

Hello, I am new to the community and although I have flashed loads of roms to various devices this is the first I have tried to build from source.
As it says in the title I am trying to build for my Oppo find 5 which there is a nightly build for, I wanted to try and build from source though.
I have set up the build environment as described on the omni website.
I have followed a set of instructions but when I come to build using
Code:
brunch find5
i dont get a zip in the out folder. I do get the following notes though in the terminal after the build.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Click to expand...
Click to collapse

Those errors are meaningless. Post the full log as an attachment please.
Although I'd suggest reading through the errors first - the first skill anyone needs in Android development is the ability to look through a log and analyze what is what.
At the very least you might've forgotten envsetup. You probably forgot to pull blobs with extract-files (or finding them through some other source...) too - nearly everyone does.

Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:

jejecule said:
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
Click to expand...
Click to collapse
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote

maxwen said:
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
Click to expand...
Click to collapse
yes i'm sure. i was first using the one from themuppets github, then Guillaume advised me to use the coyote ones. Size of the find5 vendor folder is 40,1MB, 132 files. Strangely i had this issues with my last 5 builds, but with the today one, problem disappeared and now my baseband is recognised and everything ok, though i still have this no radio.img message at the end of the build.
Really strange indeed i hate not to know what was the issue Anyway i will build again tomorrow and let you know, Chasmodo from Asylum team is also helping me a lot in understanding some stuffs as i'm a new and noob in building
One question about blobs: when i try to extract it from my device, it works when i run an 4.3 aokp build but then i get error in building. If i try to extract blobs from omni 4.4 (official nightly) i get some access denied on some blobs and then also some errors in the build. No issue with coyote ones though.
Many thanks for your time mate!

So guys, my problem with find5 modem seems to be fixed, no issue with today build neither. But.....now facing exactly the same issue with jftlexx(i9505)...
Build went OK, blobs from coyote, flash and boot OK....but no modem again, I may be do wrong stuff when flashing or missing something.
Before flashing I always do factory reset + wipe system, then flash build, gapps(pa ones mostly) + supersu.
Same repo, same vendor, I9300 OK but manually added local manifest as in your tuto.
Rebuilding atm
Thanks a lot
Sent from my Find 5 using xda app-developers app