yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab Plus] koreanschoolkid:
http://www.engadget.com/2011/05/20/...n-gingerbread-interface-enabled-by-h/?m=false

This is old news but I was wondering if anyone got this to work. I really hate the taskbar on honeycomb and usually go without it by using HoneyBar but the obvious drawback is that I have to guess at notifications or bring it back up. I tried it but it would not work for me.

The taskbar wasn't as annoying on the 10.1 but now it just feels downright intrusive to the screen. I tried StatusBar+ but that was even worse than the stock taskbar.

Maybe I'm alone on this...

US Wifi version 16gb stock, no kernals, rooted

Edit: I know I can use ADW or Go Launcher and already do. I just want that 2.x style notification bar back.
[Samsung Galaxy Tab Plus] chrisrotolo:
yes i believe this works on all honeycomb. just change your lcd denisty. there are apps that can do it or you can manually edit build.prop.
[Samsung Galaxy Tab Plus] koreanschoolkid:
I guessed as much but the video was far too fuzzy to make out which file LCD density is changed from in Root Explorer.

I tried Blade Buddy and LCDDensity from Market to get around that but no dice when set to 170 as in the video. I might have been doing it wrong however. Do you know what value is necessary to switch to the 2.x style?

And thank you for confirming that bit of information. Weird as it sounds I would rather be wrong and dumb than have the option of 2.x style left unopen to me.

Edit: Sorry my bad. Can't read. I'll try editing build.prop immediately. Although I still am unsure as to the optimal value but I will give 170 a twirl again.

Edit: I can't seem to change it. I tried editing build.prop in /system but it told me it was a read only file. So I tried opening it in text editor inside Root Explorer but when I checked afterwards it was still set to 160.
[Samsung Galaxy Tab Plus] theundeadelvis:
I used LCD density and changed it to 171 (using killall), and it worked for me. I'm using adw ex as my launcher.
[Samsung Galaxy Tab Plus] koreanschoolkid:
I just got it to work but the oddest thing was that I had no notification bar at the top. Talk about a mixture of joy and rage...

Edit: The reason for no notification bar on top was my usage of Go Launcher EX as my default. I will miss using it but it appears stock and ADW EX do have the notification bar enabled so I have no choice but to switch. Thank you both for your help. I really appreciate it.

Edit: Thank you again for all your help but does your notification bar work properly? I can't seem to get Google Talk/Gmail/Email alerts through it. I also cannot open anything in Settings.
[Samsung Galaxy Tab Plus] theundeadelvis:
Just tested email and i the notification worked.
[Samsung Galaxy Tab Plus] koreanschoolkid:
Browser, gmail and notifications all force close on me.It's really disheartening. Did you change anything afterwards? Market also force closes
[Samsung Galaxy Tab Plus] theundeadelvis:
Strange, all i did was set it to 171 dpi. Nothing else, stock kernel, using adw ex.
[Samsung Galaxy Tab Plus] koreanschoolkid:
I guess my usual amount of divine favor just made sure my situation was in accordance with the alignment of the stars.

Thank you for all your help on this. I guess I'll just have to deal with it or try a factory reset and then try again. That might be the best option.

Edit: Everything now works except Settings and Gmail
[Xoom General] henryhu:
I'm trying to flash the OTA with CWM, and the assert

assert(getprop("ro.product.device") == "wingray" ||
getprop("ro.build.product") == "wingray");

failed. I suspect that's caused by "stingray" here and there in /default.prop and other places in CWM.

I have flashed the original boot partition and I have checked all the asserts for patches, and I'm sure that they would not fail with "applypatch -c".

So is there any "wingray" version of CWM? So I can flash it and then maybe I can flash the OTA?
[Xoom General] twofourturbo:
Currently sitting in the same boat. I have a US Wifi Only Xoom sitting on HTK75D. I did have a custom kernel Installed which i removed my installing "update_US-Xoom-WiFi-3.2.1-HTK75D_stachre_v02.zip" which just installed the factory boot.img that removed the custom Tiamat kernel. Once there I attempted to install the OTA and receive your same Build.Prop Issue. I first attempted with CWR and then proceeded to Install the Tiamat Recovery that is available on http://www.droid-life.com/2012/01/1...eam-sandwich-we-have-a-flashable-zip-for-you/ and still in the same boat.

Hope we can figure this out and get some tasty ICS soon.
[Xoom General] rmm989:
Subscribed b/c I have the same problem, though I had the stock kernel. Also had problems getting it to boot into the CWM recovery vs the stock recovery, but when I'd get it into CWM, this is the error I'd get.
[Xoom General] MeridianSun:
Same here. And my Xoom was stock. I've never tried any mods until now.
[Xoom General] henryhu:
Finally I gave up CWM and went to stock recovery.

I grabbed stock rom from

developer.motorola.com/products/software

"Build HWI69 for US Retail"

, extracted recovery.img,

and flashed recovery in fastboot mode to it.

Then I flashed the OTA in stock recovery and then flashed back CWM recovery...

Now it seems to work fine... I've gained root access again by flash su-install.zip...
[Xoom General] drnoir:
Did you use OTG or SD card for flashing the ICS OTA? Or maybe something more exotic you can share with us...:p
[Xoom General] henryhu:
Nothing new, just OTG, sorry...
[Xoom General] kerry_xu_cs:
since you are using CWM recovery you can modify the OTA package without worrying the signature issue.

so,

1) extract the zip package to a folder.

2) open META-INF/com/google/android/

3) use any text editor you have to edit the updater-script file.

4) remove the assert statement

5) repack the folder into a zip package

then flash it with CWM recovery, and it will probably work

====

didn't see you following posts. nvm
[Xoom General] megabiteg:
Are you 100% sure that this will work fine?
[Xoom General] whatsamod:
Was debating this, just wondering if it is worth the time and effort?
[Xoom General] megabiteg:
Tried it already and didn't work for me.... I even made sure that the signature and the asssess options where disabled and still fails
[Xoom General] justinsch03:
For all those trying, this works!!!! Just flashed, no issues. Thanks kerry_xu_cs!
[Xoom General] kevinskocik:
Can you upload your modified updater-script file?
[Xoom General] justinsch03:
UPDATE

make sure you delete from the semicolon after the mount section, all the way to the semicolon prior to the ui_print section...

---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------

don't have the ability to upload this file...may put on dropbox later on. just to sum it up though, this is what your first line should look like....

"mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/system", "/system");

ui_print("Verifying current system...");

show_progress(0.100000, 0);

assert(apply_patch_check("/system/app/ApplicationsProvider.apk",
[Xoom General] megabiteg:
Then time to try it out again.... :D
[Xoom General] kevinskocik:
Can also confirm this works.
[Xoom General] whatsamod:
Trying to figure out I missed, deleted as stated and still failing to load. Aborts the install any ideas
[Xoom General] PaulPredator:
Make sure you edit the script in notepad++

Just confirmed the update here after doing the change in notepad++
[Xoom General] megabiteg:
I deleted the Cordy and DungeonDefenders apk & odex files, can someone post them, my install fails on the check
[Xoom General] p2flol:
Worked flawlessly. Flashed via CWM.

TY
[Xoom General] driveboy:
Glad!

Really glad for you but could you post a picture of your updater-script file or the file itself? Can't seem to install it. Using notepad++ and 7zip/rar to create the zip. Using Cwm to install it. I get Status 6 or Status 7 when trying to apply the patched update.zip. Is there a way you can send me directly your updater-script file? Please?
[Xoom General] epic118:
Confirmed, removing the getprop lines with Notepad++ and updating the ZIP with WinRAR works.

I am now installing ICS from CWM! Thanks for everything.
[Xoom General] driveboy:
Could you send the your updater-script file, please? I can't seem to get it right, the update starts but then I get a 7 error message. I'm now installing winzip to make sure It's not RAR or 7zip messing up with the compression of the file. My head hurts...

---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------

Is there a way you could, please, send me your updater-script file already edited? I'm having a horrible time trying to get it right but I still get the "7" error message.
[Xoom General] Submarine854:
After deleting those lines

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2.1/HTK75D/190830:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:4.0.3/IML77/239789:user/release-keys");
assert(getprop("ro.product.device") == "wingray" ||
getprop("ro.build.product") == "wingray");

The update process runs on and stops at this line

assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/boot:8388608:4d118f55cf5e465440969c3abfd2266ff5786a4c:8388608:1c34fcebeae2dcc1c9bf552bdf875c3e7fd497e7"));

I don't know if the script tries to modify the boot loader, I'm not a Android expert at all, however IMO, it seems it's going to happen.

If I would remove those lines, too, the update script should run fine, I guess (FYI, I didn't continue here, I just looked into the script file for similar, tegra.3, lines):

ui_print("Patching boot image...");
apply_patch("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/boot:8388608:4d118f55cf5e465440969c3abfd2266ff5786a4c:8388608:1c34fcebeae2dcc1c9bf552bdf875c3e7fd497e7",
"-", 1c34fcebeae2dcc1c9bf552bdf875c3e7fd497e7, 8388608,
4d118f55cf5e465440969c3abfd2266ff5786a4c, package_extract_file("patch/boot.img.p"));

So can I remove this single line, too or will I encounter serious problems afterwards? E.g. no booting anymore?

Michael

Edit: I'm running ClockworkMod Recovery v3.2.0.0 and have chosen "apply update from sdcard" menu item...

EDIT: Don't remove those mentioned lines with tegra.3 as this will result in a boot loop as it did just here ;-(
[Xoom General] driveboy:
I get the same error message as you. What are we doing wrong? I'm going to take a break, eat something and have a shower, my head hurts like hell.
[Xoom General] rds_sp:
It worked!!

This solution worked fine on my xoom.

Just be careful to not extract the contents and then repack. Open the delta file on winrar or 7zip (or whatever program you prefer) locate the file (META-INF/com/google/android/updater-script) copy it for an external location and edit it, removing the lines mentioned on the post.

Then copy it back to the delta file and you should be able to update using custom recovery.

If you are curious about the file after edition I have it copied to pastebin so you can take a look: http://pastebin.com/Dp0uxriK

Now just have fun!
[Xoom General] driveboy:
Can't do it, same error message as before. I'm going to go back to stock and start over because there is just something I'm not getting right. Thanks a lot for the code anyway! Obrigadao!!
[Xoom General] hpe:
Could anyone be so kind and upload a flashable ZIP and share via e.g. Dropbox? I'm editing the update-script file from my Mac, and can't seem to get it right. Pastebin here: http://pastebin.com/WZRJHWyt The message is that it has an assert fail of file "/system/app/ApplicationsProvider.apk"
[Xoom General] whatsamod:
So this is what I tried so far.

I know that I deleted files and games from stock image so I returned to stock 3.2.1 by flash file from

http://xdaforums.com/showthread.php?t=1278214

Now I have all the lovely games that I will not play back on Tablet. Then extracted the updater script and edited using notepad++ and added back into the delta file using winrar. Reboot into CWM and try to update from selected zip file. It yields an error 7 and aborts.

Basically trying to figure out what I am missing...
[Xoom General] driveboy:
Did it without the cable, tough cookie!! Even with rds_sp's code I was getting the same error message.

Restaured back to stock (MZ604_HWI69 files), locked bootloader, installed all the OTA's again, unlocked bootloader again, installed the recovery in the droid-life original post (something Tiamat) and updated perfectly. The problem wasn't in the update.zip code, the problem was something with the bootloader or the recovery. I'm enjoying it now.
[Xoom General] megabiteg:
can someone post the zip file they used please, that would be a great help.

I'm getting the same error code 7...

EDIT:

OK, found a solution for those of us that are receiving the Stop code 7. In the script file, along with making the changes to the start of the file like indicated in the first page you need to remove these additional lines:

set_progress(0.947971);

assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/boot:8388608:4d118f55cf5e465440969c3abfd2266ff5786a4c:8388608:1c34fcebeae2dcc1c9bf552bdf875c3e7fd497e7"));

you can find these in lines 785 & 786 if you open the script with Notepad++

Let me know if you have any questions.
[Xoom General] soulantrax:
Perfectly worked ! I did it on rogue recovery !
[Xoom General] whatsamod:
10 minutes at boot screen to long(boot loop) or did this take forever to load the first time?
[Xoom General] whatsamod:
Upon Boot loop went back and restored. Read that it worked on Rogue so I changed Recovery to Rogue -

When I open Rogue I get an error

E:Cant open /dev/block/platform/sdhci-tegra.3/by-name/misc

(no such file or directory)

E: cant mount /cache/recovery/command

E: can't open /dev/block/platform/schci-tegra.3/by-name/misc

(no such file or directory)

E: cant mount /cache/recovery/log

E: cant open /cache/recovery/log

May have found the issue but now how to fix?
[Xoom General] sonicemerald:
finally got it to work. I unlocked my bootloader, flashed all the way back to 3.0.1 (found out that was only to root it... but also found out that I can get into the recovery i flashed by NOT letting the xoom boot all the way up.

opened the zip,

extracted the script-updater file,

edited the file with notepad++, (just deleted the first two segments)

then copied the edited file back into the zip file,

flashed my recovery (used Rogue Recovery)

then updated, I had my file on internal storage, since my sdcard would never mount.

about to enjoy!

THANKS!!!
[Xoom General] megabiteg:
Mine lasted 5 min booting, but eventually it did.
[Xoom General] throl:
Can you post your zip somewhere? I let mine boot for 20+min with no luck.
[Xoom General] Dougrun:
running CWM 4.0x, stock, rooted, tried both modified script edits and still get a error 6 code. I'll wait for my cable I guess.
[Xoom General] tutech:
Here's the file that I modified and used sucessfully to flash in CWR 3.2.0.0 from my US WiFi Xoom 3.2.1 HTK75D to 4.0.3 IML77:

Dropbox: http://dl.dropbox.com/u/28227060/CWM_MODIFIED-tervigon-IML77-from-HTK75D.zip

4Shared Mirror: http://www.4shared.com/zip/VNNIA0J2/CWM_MODIFIED-tervigon-IML77-fr.html

I had my HTK75D build completely stock with the exception of the Tiamat 2.1.0 kernel so I could overclock, so I needed to flash the stock Motorola/Google system and boot images. I used fastboot flash boot boot.img and fastboot flash system system.img from this thread to achieve that without needing to go all the way back to wiped clean stock ROM/stock recovery and that way I could upgrade my system and keep all of my apps and settings intact. I had to fastbook to stock 3.2 HTJ85B then OTA update to 3.2.1 HTK55D then OTA update to 3.2.1 HTK75D. Then fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img from the Universal Xoom root thread and boot into CWM to flash the CWM_MODIFIED-tervigon-IML77-from-HTK75D.zip and now on IML77 =) Just needed to root it again with the Universal Xoom root.
[Xoom General] donc113:
You are not on the stock boot image. You MUST be 100% stock except for recovery. You can (maybe have to be) be unlocked.
[Xoom General] Dougrun:
thanks tutech, at least my status 6 error is gone, now i have the Status 7 error mentioned previously. I'll try that fix.

---------- Post added at 09:18 PM ---------- Previous post was at 09:07 PM ----------

tutech's file, plus deleting the status 7 error lines whatsamod posted works.

removed sd card

power on, android recovery

CWM 4.0x: update from zip file

boots into ICS! thanks guys!

---------- Post added at 09:26 PM ---------- Previous post was at 09:18 PM ----------

well, scratch that, its booting all right, but its in a boot loop, just an endless pretty boot animation, over and over.

---------- Post added at 10:02 PM ---------- Previous post was at 09:26 PM ----------

ok, so now I have my wifi xoom, with a corrupt ICS and doing a factory reset doesnt help.

I have CWM 4.0.0.4 and can boot into recovery but for some reason, it wont see my SD card so I cant ask it to load anything new or restore the GB backup that I have on the SD card.

Any thoughts?
[Xoom General] megabiteg:
Get the file for cwm 3.2.0.0 and flash it via fastboot. Then try again.
[Xoom General] henryhu:
Don't try this! Don't remove any apply_patch_check lines!

This is an incremental update, so it needs to verify that the original files are OK and then patches them.

If you failed the check of the "boot" partition, then it means that you have modified it (Mostly caused by "rooting"...). If you insist on removing the checks and applying the update, it would patch them wrongly(without error messages!), and then the contents would be corrupted. So after the update, your boot partition is ruined, and it would fail to boot!

You may flash back to original "boot" partition to solve the problem.

For the check of getprop, that's safe to remove, since your real system is "wingray" which satisfies the check. It's just that CWM reports your system as "stingray" which fails the check.
[Xoom General] doughnut1:
Iam not convinced its linked to boot image.

I have a stock HTK75D on a wifi Xoom, all i've added was the recovery image from Rogue, which I installed from fastboot.

Its drops out of the procedure when checking that final assert line sdhci.

I also concur with Henry, that remove this line will give you a boot loop of ICS
[Xoom General] tutech:
Follow what I said (CWR 3.2.0.0 plus all the rest I said) or try to use stachre all in one CWR update.zip he posted: http://xdaforums.com/showthread.php?t=1446469
[Xoom General] zytho:
Thanks!

Awesome instructions... Works like a charm. :)
[Xoom General] rmm989:
Worked flawlessly, thanks!
[Xoom General] doughnut1:
+1 works a charm indeed, no idea what i was doing wrong previously :(

I did use Rogue instead of CWM by the way
[Xoom General] Dougrun:
thanks, went to cwm 3.2, recovered to backup, flashed stachre's all in one and it works great.
[Xoom General] megabiteg:
I do agree with you that its a dangerous what I'm suggesting but if you've covered all your bases of returning to a stock kernel and not having a custom ROM when you'll attempt the update you should be fine... it worked for me.

Plus that segment is just a check point just as the two lines we removed at the beginning of the script.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 32dave:
Has anybody tried Super charger from Zepplinrox on the S2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bacheezy:
S2?

To exactly which version S2 are you refering?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 32dave:
The i727 skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] yvrRome:
I used it on my SGS but haven't tried on my SR since I don't see the need for it.
[LG Nitro HD] thatg:
So ive been using one for a couple of days now. Love the screen, ergonomics and volume of the ringer, thats about All the praise ive got. Heres the bad stuff, the earpiece is not so great, it tends to crack. The permformance is pretty sluggish for a 1.5 dual core. There seems to be a second or 2 delay in everything i select, which is by far my biggest issue. And then the battery life is not so hot but i could live with it if the phone were more snappy.

I'm going to sell mine but i cant wait for some development and cm9 for this phone. I think its hardware has a lot of potential but something is really dragging the performance of this phone down.

Am i the only one that feels this way?
[LG Nitro HD] scott0:
I am very satisfied with this phone, coming up on 2 months of use. I don't have any of the issues you have with yours. A 2 second delay for everything you select? I'd sell that phone too.
[LG Nitro HD] theoski:
Same here. I look now at none hd screens and I cant take them. I noticed that on CES lots of announced phoned had this same specs as Nitro that I have had for two months. You get the point. I am more satisified with this purchase than I was with Atrix 4G with lapdock at this same point the last year.
[LG Nitro HD] bmxant:
I'm also fairly satisfied after doing a bit of tweaking. @ thatg, are you running completely stock?
[LG Nitro HD] thatg:
I was stock rooted. Tried all kinds of launchers but after coming from the galaxy nexus it just felt like the phone was being held back. Back with the 4s till htc makes something with ics or cm9 comes out for the nitro and ill give it another go
[HTC Flyer, EVO View 4G] xenix96:
WARNING: This procedure applies to View only with Official OTA HONEYCOMB Update.

Just do this Honeycomb to gingerbread downgrade for Official OTA [Procedure up] and u are on Gingerbread back again ^^

And thanks to globatron :cool:
[HTC Flyer, EVO View 4G] globatron:
probably better to try this one first:

http://xdaforums.com/showthread.php?t=1428106
[HTC Flyer, EVO View 4G] jmboulware:
Globatron ... both links for tacoroot are giving me errors ... would you mind taking a look?

JB
[HTC Flyer, EVO View 4G] globatron:
They work fine for me.
[HTC Flyer, EVO View 4G] jmboulware:
This is what I get with Multiupload ... the other just never loads. Would you happen to know of another link?

View attachment 863979
[HTC Flyer, EVO View 4G] legend221:
Hello globatron,

Please re upload anything exclusively to megaupl*ad; site is officially shut down :mad:

http://www.bgr.com/2012/01/19/megaupload-com-shut-down-founder-charged-with-violating-piracy-laws/
[HTC Flyer, EVO View 4G] globatron:
Megaupload has nothing to do with me, I have never uploaded directly to megapload.
[HTC Flyer, EVO View 4G] mcord11758:
Dark day with bad long term ramifications. Hopefully they beat the case and set a strong precedent
[HTC Flyer, EVO View 4G] jmboulware:
This may be a good lead for Tacoroot since the mega upload link is down:

https://github.com/CunningLogic/TacoRoot

JB
[HTC Flyer, EVO View 4G] legend221:
Great news.

Some do, that's the problem

Stay awesome mate :D

---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------

Im with you.

Nothing worse than the government trying to police the internet.

Its just bad all around.