yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] cellzealot:
What is the exact error message? They are very specific and will tell you precisely which file fails the assert check.

Also, did you use moto-fastboot to restore the webtop partition?

That is what I had to do because I am using the webtop hacked apks for any HDMI. If you have altered the webtop partition at all you will have to do likewise in order to get the full 5.7.893 to install.

Other users have had issues with the preinstall partition and have had to restore that first as well.
[Motorola Droid Bionic] open1your1eyes0:
Interesting...but I'm assuming they wrote that before knowing that you could downgrade the radios. I wonder if that's what's making it fail. I will try this specific file tonight either way and get back to you guys. My goal is to get to one complete build, no matter what version it is, even if it's possible to go to 5.6.893 or 5.8.894 I will attempt that as well. I will try everything I can before trying to ship it out to Motorola. Please keep posting anything you guys think might be useful or worth trying.
[Motorola Droid Bionic] cellzealot:
The best you can do is to restore 5.7.893 with the updated radios for that build.

I have been through this multiple times as have many others and have reverted the radios to stock 5.5.886 and gone forwards again.

Sometimes it's actually useful to listen to the experience of others and get complete information before beating your head against the wall to prove it to yourself. ;)
[Motorola Droid Bionic] open1your1eyes0:
I don't remember the exact message now (I believe it was something mentioning like "assert failed apply patch check" and then long string of characters, tmp/sideload/package.zip error, and Status 7 at the bottom) but I did figure out to get moto-fastboot (after getting the "data too big to fit into memory" error in fastboot) and I was able to restore the 886 webtop and 886 preinstall (in fastboot) as well. I flashed every file I could in the FXZ through fastboot, the only ones that I remember that didn't go through were cdt.bin, boot.img, recovery.img, and a few other minor ones I think).

Duely noted...usually I'm not afraid to try it anyways because with almost every HTC device I had where I messed something up with was always reversable. I guess this is just an isolated case with Motorola. I'll be sure to take good note of this for future reference.

So you're saying that the radios should be able to update either way? I'll be sure to try again tonight then.
[Motorola Droid Bionic] open1your1eyes0:
Hmm what an interesting coincidence that we should be talking about leaks:

DROID Bionic Receiving Mysterious 5.9.901 Update?

Link to file

Can this be of any use to us here?
[Motorola Droid Bionic] SamuriHL:
ROFLMAO! If you only knew. sigh. :) I spent several hours on it last night. No, absolutely no help at all I'm afraid. I tried getting around it multiple ways and basically it sees the boot image and says "no. Just no." So, no help there.
[Motorola Droid Bionic] open1your1eyes0:
Have you tried looking for this build in cheesecake? That way it'll download the version for your OS. (Assuming you're still on a complete matching build)

It looks like that file is only if you have the complete 5.5.893 OTA installed.
[Motorola Droid Bionic] SamuriHL:
Yeaaaa, I did a LOT of stuff last night. :)

1) Checked cheesecake....says I'm up to date

2) Tried to flash 5.9.901 in stock recovery, failed prop file check

3) Reverted to 886 system, upgraded to 5.5.893 system using a CWR image, and then tried to flash 5.9.901 in stock recovery. Got a different assert failed basically saying that the boot image doesn't match

So, yea, I tried quite a bit. All failed. Until we get a boot image that will flash over the top of the 5.7.893 boot image, we're all screwed. Period.
[Motorola Droid Bionic] open1your1eyes0:
Yup very true. Thats the looks of it. No wonder cheesecake hasn't been showing me any updates for the longest time. I can't even find 5.8.894.

Is there a file like that? (5.7.893 to 5.8.894)

At least we nailed down the issue...this thing has been driving me crazy figuring out what was going wrong. Now I just have to try to get back to a full 5.7.893.
[Motorola Droid Bionic] SamuriHL:
There is no file that will get you off of 5.7.893 at all. How very frustrating is that? One can only hope that Moto leaks one or someone finds one that will take 5.7.893 and bring us back to the upgrade path. Maybe now that 5.9.901 is pushed they'll consider it. Wouldn't that be a nice Xmas present. :D
[Motorola Droid Bionic] cellzealot:
No there is not an incremental update from any of the cheesecake builds, that is the entire issue.

And FWIW, we have both been trying to tell you all of this for several pages now.

It is pretty well understood at this point why the updates fail and what we can and can't do to remedy the problem. What was proven again last night was that the new 5.9.901 update does assert the system and boot from 5.5.893 but does not assert /system/bin/mount-ext3.sh, so permanent root methods work to keep root after the update.
[Motorola Droid Bionic] open1your1eyes0:
Could have sworn I recall one a while ago but I'm probably imagining things. :/

Understood. Well that's good to know.

Well....here's to hoping that 5.7.893 will be an actual OTA some day.
[Motorola Droid Bionic] SamuriHL:
Uhhhhh, no? We're now already well past it. 5.9.901 is much newer. There'd be no reason to go back. So yea, our ONLY hope is that a future update allows us to update over 5.7.893. Until then, we're screwed. And will remain so.
[Motorola Droid Bionic] open1your1eyes0:
Well yes my point was we need 5.7.893 to be an official OTA for us to ever move forward. That way there will be updates in the futures over the 5.7.893 build. As far as I understand, this 5.9.901 is not really official yet so there's still hope.
[Motorola Droid Bionic] cellzealot:
I hate to quote myself to make a point...but there it is from page 4 and my first post in response to this thread.

That is what we need to solve the issue...not for 5.7.893 to become an official OTA. All they have to do is change the asserts in the script to allow for the signed components in 5.7.893 to pass through and be updated.

Or a new full XML.zip containing all of the signed images and files required.
[Motorola Droid Bionic] SamuriHL:
Oh there's always hope. Moto could very easily push an update to the 5.7.893 users to get them back on the path. Will they? Who knows. We just have to wait.
[Motorola Droid Bionic] open1your1eyes0:
These are both true but unless 5.7.893 is an official release, would they really have a reason to do this? I mean let's face it, if you currently have a 5.7.893 build, you did something you weren't supposed to. Really unlikely Motorola is even aware of this an issue or would want to support us in this case. I think the only hope aside from an official release is if one of the insider testers from Motorola that worked with the 5.7.893 build has an FXZ or incremental update (or like what cellzealot stated) and leaks it. Other than that, I wouldn't get my hopes up on Motorola supporting unofficial leaks (we have bad enough support on official builds, cue. locked bootloaders, downgrade checks, etc...).
[Motorola Droid Bionic] SamuriHL:
It's not impossible. It's not like this is some hacked version that a dev put together. This is an update that they wrote that leaked. It was properly signed by moto. Should we have installed it? Not at all. But the fix is easy enough for them to handle. All we need to do is wait and see what happens. If there's no fix in a month or two then we know we're screwed and left in the cold. And I will take that lesson to a new phone with an unlockable bootloader. :) But I don't think we should give up hope yet. Not by a long shot. There are a LOT of people in this boat. Patience. Isn't the lack of them what got us into this mess in the first place? :D
[Motorola Droid Bionic] open1your1eyes0:
I take my words back. QFT :cool:

Guess I'm going to really hope now that I can get back to 5.7.893.
[Motorola Droid Bionic] SamuriHL:
Yup. One step at a time. Try the things we outlined earlier and see if that puts you back on 5.7.893 and then stay there if you're successful. In fact, back it up with CWR. :) You think I'd have tried all the stuff I did last night if I thought i couldn't get back to 5.7.893? God no. I'm stupid (see about system showing 5.7.893 for proof LOL) but not THAT stupid. :D Always make a good backup. I still have a backup of my original rooted stock. A lot of good that does me. sigh.
[Motorola Droid Bionic] open1your1eyes0:
OK so I'm home now.

Just restored and flashed everything to 5.5.886. About to apply that 5.7.893 update now. *crosses fingers*

EDIT: It worked!!! The update applied and updated the radio files as well! :D
[Motorola Droid Bionic] open1your1eyes0:
By the way I noticed a few files in the FXZ that were unaccounted for in the default_flash_targa.xml file. Maybe someone can elaborate on what they are for?

"fastboot"

"motoboot.img"

"userdata.img"

and inside a folder called "ota" the following files:

"bp.img"

"fotabota_includelist.cfg"

"fs_config.cfg"

"lte.img"

"updater"

Any idea what they are or what they're used for?
[Motorola Droid Bionic] SamuriHL:
Now.....go to your room and NANDROID that thing. :P
[Motorola Droid Bionic] open1your1eyes0:
Well, honestly I'm going to be selling this thing soon so right now I'm not touching it anymore. I'm leaving a clean OS. I just have to decide if I should bork it and RMA it with Motorola and sell it later or sell it as is.

Sidenote: I found this 5.8.894 update as the same file I just used to update to 5.7.894 from 5.5.886. Do you think it's possible if I return it to 5.5.886 and update it to 5.8.894 (even though it'll contain a few 5.7.894 files)? Or it will fail check?
[Motorola Droid Bionic] SamuriHL:
It will fail.
[Motorola Droid Bionic] open1your1eyes0:
Good. Because I'm feeling lazy now anyways. :p

Thanks for all your help and information guys. I think I can continue on from here. :)
[Motorola Droid Bionic] SamuriHL:
You're welcome. Glad you're back up and working again.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] sharp910sh:
I just noted (pardon the pun) that there are lines vertical ans horizontal lines when displaying white. This is my second phone. I went back to cpw and changed this one has similar horizontal lines. Its very very very faint, but I can see it. Im not sure why, it is because of the AMOLED screen, how it works?

Very annoyed. what can i do? every phone CPW has cant be faulty?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nuclearmonkeyuk:
I've only had mine a day but cant see any lines like you've mentioned... maybe a bad batch they got in? Maybe something to do with the S-pen's digitizer screen, i assume that will have some form of grid to it
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SonicTab:
AMOLED seems to have weaknesses at low brightness levels.

Some have seen very faint lines .

Also on minimum brightness some reported a faint changing of the hue of the display.

The screen is also very bright (whites) on min brightness.

If you display a greyscale step pattern black is absolute black but

others that should be near black are too bright.

http://www.execulink.com/~impact/docs/utils/StepGray16G.jpg

I think its just the AMOLED tech but check the display thread too.

In normal use the screen is amazing,

all technologies seem to have good and weak points if you look for them.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SrAdama:
You are not the only one with this problem. I'm on my third galaxy note now... The first one had dead pixels and the right side was darker than the left side. The second one had much more dark horizontal and vertical lines and smudges. The third one at first had very faint lines and smudges, but it is becoming more visible now. There are several threads about this issue on this forum.. My guess is that these problems are pretty widespread (more or less visible on some gnotes) and that there were some bad batches or that the Amoled technology is the problem. Would love to hear the reason to these issues from Samsung.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ITPiraten:
No lines on mine. White is white and everything shows up excellent.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] MartijnMM:
So you tell me you don't have banding at all?

No ****ty black-grey in videos?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nuclearmonkeyuk:
Depending on the source if I'm watching say the end credits (white words on black screen) they get like a greyish glow around them
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ITPiraten:
AMOLED limitations, ppl!

If you disable the automatic light control and just snap the backlight up from 0% to anything above, you will not see any grayish things in video on the Note. I don't have this problem, but I've heard that some people have had to do this to solve this issue.

I don't have any bandings or strange lines anywhere on the screen. It looks as good as my Galaxy S II and Galaxy Tab. I haven't seen anything out of the ordinary (considering the limitations of the AMOLED screen).

There have been concerns about the lines on the white though. I don't have any of those on mine, but it seems some screens show up this fault. I don't know how to solve this issue and would recommend returning it as soon as possible.

Using the recommended gray test on the Note didn't show up anything but a solid grey screen on mine, although I've heard much people have dark spots all over. It might be something about where the phone was manufactured, or when.

My Note have never had anything wrong with the screen or anything else. The only problem I've ever had is applications that use 16 bit color instead of the Notes 32 bit. This will make color look strange at times, but it's totally normal.

Note that this isn't something wrong with the hardware, it's merely a software problem that will be solved as soon as ICS is released.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] MartijnMM:
Check this video, you REALLY have no artifacts?

Lines/spots are due to ****ty quality control, this is just a matter of luck.

I have yet to see ANYTHING with more then 65k colors, even in the browser.

All i see is some VERY clever dithering very hard to see due to the high resolution.

Coming from the HD2, I'm really disappointed, nothing gained in 3 years (well, more pixels, so harder to see the flaws).

I took 3 picture with a green gradient:

1) 1280width, so basicly 1280 levels of green, but 24bit only shows 255.

2) 255width, so basicly 255 levels of green, 24bit.

3) 64 width, so basicly 64 levels of green, 16bit.

They all look the same to me, in browser and in gallery. I see dither in each of them. This tell me the whole screen is 16/18 bit only.

Maybe the PenTile is playing tricks with me...

Or the grainy screen lets me think its dithered...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] splurge_in:
i am facing a similar problem..whenever i apply some photo having a lot of black in it as my lock screen image..there seems to be some horizontal gray lines in it..but when i look in the gallery the black is pure black (no horizontal gray lines at all)...is there any problem in the software only ? or is it something regarding the screen?
[Samsung Galaxy Nexus] jetrii:
This notification comes up after most of my boots and takes anywhere from 3-10 seconds to go away depending on how many applications it is upgrading. What exactly is it doing?
[Samsung Galaxy Nexus] AmesCell:
http://xdaforums.com/showthread.php?t=1365133&highlight=upgrading
[Galaxy S II Q&A, Help & Troubleshooting] yongjie222:
Hi all, recently, i have encountered lagging/freezing while typing or sending a text, for example i were to compose a message, i can type it without lag, but when i clicked send, it freezes awhile and the message takes awhile to show up being sent, after that when i proceed to send another message right after sending, i experience lag while typing the texts, it freezes for awhile but i continue to type and it come back with all the letters coming in quickly. I have tried different message apps like Handcent, Go sms and the default app.

I am using Checkrom v4 and siyah 2.5.1 kernal by the way, has it got to do with them? I experienced this problem a little before flashing custom roms but after that the problem became more significant. I tried wiping and reflashing again its still the same.

While other usages on the phone i do not experience any lag, only applies to texting.

Help would be appreciated ! Thanks.
[Galaxy S II Q&A, Help & Troubleshooting] bala_gamer:
Has nothing to do with kernel nor rom. Check your background process, something is using your cpu a lot. Also try clearing the data and cache for messaging.
[Galaxy S II Q&A, Help & Troubleshooting] yongjie222:
I checked and there are no running programs, i do have a lot of messages, how do i clear the cache? Means clearings all the messages? I would like to preserve the messages but without causing lag? Is there anyway to do so ? Others than backing up with apps. Thanks.
[Galaxy S II Q&A, Help & Troubleshooting] hypermagz:
my way of removing the lag on messaging is to turn on force GPU rendering(settings>developer option then tick force GPU rendering for app) that's it you will not feel any lag on your text messaging anymore. hope that helps.
[Galaxy S II Q&A, Help & Troubleshooting] cabbyz:
If you go to Settings - Applications

Choose All

Then scroll to messaging

It will tell you there how big your cache and data is for this app.

I believe if you clear data you will lose all your messages but not if you wipe the cache. It is advisable that a lot of messages will lag your message app as it needs to load everything
[T-Mobile Samsung Galaxy S II SGH-T989] darkside79:
Ok, I was running

[ROM][STOCK] Deodexed KL1 with Wifi-Calling [Team Kang][12.14.2011] and T989UVKLI MODEM but switched back to Juggernaut 3.7 because I was having some pretty bad bugs with that ROM! First really bad Browser Lag on Stock Browser. And also tried playing Dungeon Defenders Second Wave but having Major Graphic issues. All green and yellow graphical issues. Also noticed my 4g//3g service was dropping service alot more!

Did a fresh clean install too. No difference. Anyone have any ideas about a fix or how about a different KLI ROM that does NOT have these issues! Thanks a million!
[T-Mobile Samsung Galaxy S II SGH-T989] tigerz0202:
i had the deodexed version and had same issues so i just went back to the odin version which isnt deodexed but i had no issues with it
[T-Mobile Samsung Galaxy S II SGH-T989] darkside79:
Also streaming videos seems to be messed up. graphical issues and loading issues! Anyone else have these issues on T989UVKLI ROM?
[T-Mobile Samsung Galaxy S II SGH-T989] darkside79:
Odin version working good then? How do you get root access on that version? what files do I need thanks a million!
[T-Mobile Samsung Galaxy S II SGH-T989] rickm8384:
Revert to stock using Bubby's method. Then Odin the update. Finally re-root using the original method that we all used when we first got Root. All of the steps can be found in the development section.
[T-Mobile Samsung Galaxy S II SGH-T989] chib1panda:
Follow this link to root via odin. http://xdaforums.com/showthread.php?t=1311194
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
Or you could just flash this in recovery. Its odexed and I haven't had any issues with it.

http://min.us/mwFjU0qJe
[T-Mobile Samsung Galaxy S II SGH-T989] darkside79:
Is that the same odexed Rom I had problems with? browser lag and game issues?:confused:
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
No. you said in the op you flashed a deodexed. And there is no issues with the one I linked
[T-Mobile Samsung Galaxy S II SGH-T989] Lakeshow423:
Thanks for the link Mike!
[HTC Sensation] vincepg13:
Ok so from trolling around the forums I've found quite a few people are having problems with sense 3.5 and blurry contact pics. Some people managed to get clear ones, but most aren't so lucky...so here's my challenge:

The problem arises from the link between Facebook for HTC sense and Facebook for android in sense 3.5. In short sense fb gives nice clear photos like on sense 3 and android fb gives blurry pixelated ones when enlarged from the contact size in people app...e.g there blurry on incoming call.

So my challenge to anyone that thinks its possible is: can we unseparate these two forms of Facebook so it is like it is on sense 3.0? Common sense tells me this should give clear photos again as we can sync with fb for HTC sense.

I've mentioned it in various threads and got different answers so anyone that thinks its possible/not possible please share your views.

Sent from my HTC Sensation XE with Beats Audio
[HTC Sensation] KAwAtA:
I'm on sense 3.5 and all my pictures are clear. One thing I've noticed though is if I add a facebook account after my phone is set up, sometimes my contacts are blurry. If I set up facebook when I enter in my gmail account and everything at first start up.. it works fine. Try that? But like many others (I'm assuming) the pictures aren't blurry. They are a bit but I don't think that part can be fixed. Even the photos I've taken and attached on seperately aren't super clear when they call. However, it's not bad
[HTC Sensation] the_scotsman:
Yea, mine are clear too...but the issue is, is when someone on your contact list calls you, on the screen their picture is blurry on the "incoming call" display.
[HTC Sensation] vincepg13:
Call someone with a pic, there massively blurry for me. All my pics come from Facebook ya see. And fb for HTC sense is way clearer on sense 3 then fb on 3.5

Sent from my HTC Sensation XE with Beats Audio
[HTC Sensation] vincepg13:
Even if you do or don't get this I just wanna no if its possible to separate the 2 fb apps

Sent from my HTC Sensation XE with Beats Audio
[HTC Sensation] fireishott:
I fixed this issue I don't use facebook but do use Twitter still think the concept is the same just by going into the contact edit page and selecting the pic and it comes up with a drop down box and I select the Twitter for HTC sence and the contact pic is nice and clear but I do have my contacts linked
[HTC Sensation] vincepg13:
Yer that's because thev have left Twitter for android and peep (htc sense Twitter) unlinked.

I.e. go into accounts & sync and both the accounts are there. This isn't possible for the Facebook one. The accounts only show one and so do the contacts

Sent from my HTC Sensation XE with Beats Audio