yashsingh1/xdaforums huggingface dataset:
[Flipside General] xaser66:
Hi!

Well, I belive that I may remenber a similar issue some months ago... I dont remenber well how I really fixed and I almost sure that it fixed by reflashing again with froyo, sine this is the only resource that I had to try it out... also seems that when You upgrades to Froyo is not possible to downgrade/return to a previous android version (and it seems that is not only in FlipSide, so seems the same for other Moto models...)

so, by the way, I may suggest... Remove Your SiM and SD memory cards, Put the phone in flash mode an reflash the froyo again, and also backup you personal files from Your SD memory card and erase everything from SD memory card (prefer reformat your SD card) and then when Your phone reboot normal and after an initial setup BEFORE recopy your personal files, AGAIN reformat WITH YOUR PHONE MENU OPTION Your SD card and do an factory restart... may sounds silly so lot of erase and wipes... but in my case, after this such harsh cleanning make my trouble phones working fine and stable again, and after that I restore again my personal files to my SD card.

Good luck and best regards!
[Flipside General] thebluetoothkid:
THanks, I think you're onto something with the SD card. I remember months ago I had an issue with the phone rebooting if I had this one certain SD card in my phone. Thanks for the help and joggin my memory.
[HTC Sensation] skhan33:
How to increase the touch vibration level in the normal HTC ? It is too low and I could not find it anywhere.
[Samsung Galaxy Nexus] DrZEUS:
I own a Rogers GSM Galaxy Nexus that originally came with 4.0. I had since manually updated it to 4.0.2 yakju, but kept the stock radio it came with (UGKL1).

Today I received an OTA update notice for 4.0.4. I proceeded to do the update but it failed (android on his back with stomach open and red exclamation mark). Phone reboots and 4.0.2 still remains.

Tried this 4 times and same result.

Could it have anything to do with the stock radio not being updated to the 4.0.2 version? What could be the problem and how do I go about rectifying it?
[Samsung Galaxy Nexus] El Daddy:
You need the stock yakju 4.0.2 radio for it to complete the OTA.
[Samsung Galaxy Nexus] efrant:
As El Daddy said, for that update to work, you need the radio that came with 4.0.2, as well as the kernel, recovery, and all the files in /system that came with 4.0.2. If you made any changes, it won't install.
[Samsung Galaxy Nexus] Madshammers:
I have the same issue, but I'm in Australia, if I reflash the radio, will I brick the phone?
[Samsung Galaxy Nexus] martonikaj:
No....
[Samsung Galaxy Nexus] Delphi:
Hi there, I'm on the german 4.0.2 (ICL53F) stock-rom and here the OTA update to 4.0.4 fails, too... lying android with open chest + red "!" in a triangle.

The only thing I done was rooting the phone via the method I found here: http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html

Any way to log what happens?
[Samsung Galaxy Nexus] JayDaKissEP:
Everybody and there mother knows that you cannot except an Over-the-Air update on a rooted phone. You either need to unroot your phone and go back to Stock or wait for someone to post a flashable .zip
[Samsung Galaxy Nexus] efrant:
I hate to break it to you, but you are incorrect. Having root does not impact your ability to accept an OTA update (but you do need to be running a stock rom, rooted or not).
[Samsung Galaxy Nexus] Delphi:
That is exactly what I thought myself. But it looks like that it's not a big help, where can I find the OTA-update if the phone has downloaded it? Under /cache ?

And it sounds like I need a custom recovery to manual apply an update?
[Samsung Galaxy Nexus] efrant:
Yeah, it will be in /cache. But it is easier to just go here, download it and flash with CWM. Note that you will still need the ICL53F stock boot image and the XXKK6 radio flashed.
[Samsung Galaxy Nexus] Delphi:
As far as I can see, basebandversion and build-number fit with the stuff that is already on the phone.

Thanks for the link! Btw: what does those names stand for? Kinda worried I pic the wrong one... is yakju IMM76I from IMM76D the 4.0.4 for the GSM Nexus?
[Samsung Galaxy Nexus] efrant:
Look in Settings->About phone and read the build number. If it says ICL53F then you need the yakju one (and more specifically, you will need the yakju IMM76I-from-ICL53F one). If it says something like ICL53F.I9250XW.... something or other, then you are not on yakju and you will need to look at the build.prop file to see which exact build you are on.
[Samsung Galaxy Nexus] Delphi:
Seems good:

Thanks for the info! :)
[Samsung Galaxy Nexus] efrant:
So yes, you need the yakju update. All the instructions are in the other thread.
[Samsung Galaxy Nexus] Delphi:
Okay, this is odd. I made a factoryreset, wiped all caches and stuff and tried to install the OTA-update:

I also tried to update manually with fastboot under Windows7 x64, but all I got was this:

C:\Users\USER\Downloads\fastboot-and-adb>fastboot flash bootloader bootloader-
maguro-primela03.img
sending 'bootloader' (2308 KB)...
^C
C:\Users\USER\Downloads\fastboot-and-adb>adb devices
List of devices attached

C:\Users\USER\Downloads\fastboot-and-adb>adb devices
List of devices attached

C:\Users\USER\Downloads\fastboot-and-adb>fastboot devices
XXXXXXXXXX fastboot

C:\Users\USER\Downloads\fastboot-and-adb>fastboot flash bootloader bootloader-
maguro-primela03.img
sending 'bootloader' (2308 KB)...
^C
C:\Users\USER\Downloads\fastboot-and-adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s

C:\Users\USER\Downloads\fastboot-and-adb>fastboot flash bootloader bootloader-
maguro-primela03.img
sending 'bootloader' (2308 KB)...
^C
C:\Users\USER\Downloads\fastboot-and-adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s

C:\Users\USER\Downloads\fastboot-and-adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s

C:\Users\USER\Downloads\fastboot-and-adb>fastboot -w update image-yakju-imm76i
.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0A3C233F1200700D
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4148 KB)...
^C

As you can see, I had to CTRL+C to cancel it (waited 20 mins) and ADB doesn't find the phone, only fastboot. Nothing happens after it starts to send the file...

Any ideas?
[Samsung Galaxy Nexus] efrant:
I'm not clear what you are trying to accomplish. You mention updating, but it does not seem that you are following the right procedure.

Are you trying to update your current build from ICL53F to IMM76I (if so, see here), or are you trying to flash a full IMM76I ROM (if so, see here). All required instructions are in those two threads.
[Samsung Galaxy Nexus] Vankog:
I found the problem!

The exact same with me.

Additionally I am using Voodoo OTA root keeper.

After the failed update procedure, I am back in 4.0.2 ICL53F, but the system is pretending the system is up to date oO

But I think I have found the problem:

After checking the Log-File in /cache/recovery/ the problem is clear to me:

The checksums of the stock-APKs do not match and therefore cannot get patched.

Reason: I am using Titanium Backup Pro and I have integrated the market updates of system-APKs (like the Bookstore or Youtube) into the ROM. Therefore the APKs are not the same any more and the checksum check fails.

Unfortunately there is no way to undo this. Especially I have no idea which app-updates I have integrated into the ROM so far.

Is there a way to extract the system APKs from the stock-image, so I might restore them manually via a root explorer?

Or can someone provide the system apps, that are updated from 4.0.2 until now? As far as I can remember there were only a few updated system apps, so it could be managable.

Could anyone with Titanium and 4.0.2 check, which system apps have this "Update" notification and can provide the list (or even the stock-APKs) to us?

This would help a lot. :o
[Samsung Galaxy Nexus] bartek46op:
Hello, i changed yakjuxw to yakju using this how-to: http://gayward-concepts.com/how-to-update-from-yakjuxw-to-yakju

Today system showed me information about update and I applied this and have problem:

http://www.youtube.com/watch?v=MT7hqGDvzsY&feature=youtu.be

Smartphone waited a while and started normal Android boot. Please help.

My phone info:

Radio: I9250XXLA2

Kernel info:

3.0.8-g034fec9

android-build@vpbs1 #1

SMP PREEMTP Tue Mar 13 15:46:20 PDT 2012

Compilation numer: IMM76D

Fingerprint: google/yakju/maguro:4.0.4/
[Samsung Galaxy Nexus] efrant:
Did you even read the update thread that I've linked to so many times in this thread? All the instructions are in there, including how to extract stock files...
[Samsung Galaxy Nexus] bartek46op:
Oops, sorry :( My glasses :cool:

But I can have clean Android without any mods if before manually change to yakju from 4.0.2?

Ok I see: http://xdaforums.com/showthread.php?t=1631190
[Samsung Galaxy Nexus] Vankog:
I did, but only the first post. How could I have know that the extraction of stock-files is described in there?

Nevertheless I'd still need trial and error to get a list of all my changed files. Or does anyone knows a way on how to get a diff?
[Samsung Galaxy Nexus] efrant:
If you would have read the first post, you would have seen that it IS in the first post...

If you've changed a lot of files, maybe just back up your data, and just flash the full version instead of trying to update.
[Samsung Galaxy Nexus] Vankog:
OK, now I see.

I did not recognized it, because the heading says "HOW TO FLASH" and I don't want to flash. Therefore it is a bit buried.

Yeah I know, but it shouldn't be so many. Only a few apps were updated so far.
[Samsung Galaxy Nexus] efrant:
Maybe I'll split it out to make it more obvious. (Although I really would hope that people would read the entire post before attempting anything, as I had suggested at the beginning of the post...)

Well, I guess go one by one. Replace the files you know you changed, and then boot into recovery and try the update. Every time it fails, you will know which file caused the fail and you can then replace it. I don't really know of an easier way.
[Samsung Galaxy Nexus] Vankog:
Yeah, I was thinking about this way, too. I'll see where it leads me to...
[HTC Amaze 4G] probablecauz69:
can someone please help me out here. i want to get rid of the god awful boot animation on the new ics leak. i have tried to copy over the one that's there now and it wont allow me to. i have also tried to delete it and that doesn't work either. any help would be greatly appreciated. :D
[HTC Amaze 4G] Turboboxer:
System/customize/resource

Drop it in there and make sure it is named TMOUS_bootanimation and you will be all set ;)

Oh I think there is an audio file for the annoying ass TMO jingle. Kill that too.
[HTC Amaze 4G] probablecauz69:
ok i will check that out. many thanks!!!!
[HTC Amaze 4G] Turboboxer:
No problem I HATE that damn boot noise so I looked into this yesterday.
[HTC Amaze 4G] porkchopexpress:
What is the best way to get in there and change the files around? I downloaded Android Commander on to my computer and even though it lets me downloads files to my PC, it won't let me do anything to the android system files because it says I need root, even though I do in fact have root.
[HTC Amaze 4G] probablecauz69:
i just put it on my sd card and then es file explorer to move it over on the phone
[HTC Amaze 4G] Turboboxer:
Download to SD. Then I use root explorer. PM me your email. I got some goodies for you. :D
[HTC Amaze 4G] probablecauz69:
ok i am able to change the boot animation and got rid of the t mobile jingle. now i want to add my own audio file during the boot animation. what do i need to name the file to work properly. i named it just like the t mobile jingle sound but that didnt work. any help would be greatly appreciated
[HTC Amaze 4G] porkchopexpress:
The T-Jingle is just a ringtone, the bootup sound is named ruby_something, I don't remember what exactly off the top of my head, but it is a .wav file.

If I am going to put my own boot animation in here, can I just find a GIF of the appropriate dimensions and rename it .zip, or do I have to take each frame and convert it to a .png and put it in a zip file the same way that the default boot animation is?
[HTC Amaze 4G] probablecauz69:
no actually T-Jingle is the sound that was used on the original boot animation. as soon as i got rid of it that jingle did not sound when i loaded up the boot animation. i know the .wav file you speak of though. but if that was the boot animation sound why wouldn't it sound now with my new boot animation. there has to be some way to associate the new boot animation with what ever sound file when the phone boots up. as far as creating your own boot animation there are a lot of tutorials on this site. within the boot animation zip file there is a text file that basically tells the screen resolution and how as well as the frame rate and how the file should work. you should dl any boot animation and look at the desc.txt file. that will give you a little of an idea of how it all works.
[HTC Amaze 4G] porkchopexpress:
Weird, on my phone T-Jingle.ogg is just a 3 second clip of the T-Mobile jingle ringtone sound, the one that plays on my phone at startup was ruby_something.wav, which is much longer and has the sort of rocket blast sound at the beginning and then a prolonged T-Mobile jingle.

I will open up the default boot animation and see what's doing. It is kind of confusing though because in the zip file is all of the .png files for the animation, but then there is another .zip file that has the exact same thing in it.
[HTC Amaze 4G] probablecauz69:
answered above in your quote
[HTC Amaze 4G] assface2009:
sorry for bringing up a fairly old thread, but this is exactly what i was looking for.

so i was able to change back to the stock boot animation as OP said, but I DO want the original sound to it, right now there is no sound. what is the file called and where is it located? i found the file in a t-mobile bloater zip from another thread, just no idea where it goes and what it should be called.
[HTC Amaze 4G] assface2009:
Bump
[HTC Amaze 4G] mike102871:
Im also looking for the answer, where does the sound file go?
[HTC Amaze 4G] Dark Nightmare:
Did any of you read anything I posted? The wav file I posted is the default boot sound.
[HTC Amaze 4G] mike102871:
Ithink you quickly answered without knowing what i and last poster asked, where in the boot animation zip does the sound file go, the link you gave me has the sound file seperate from the bootanimation zip.

I read every post in this thread and my question is not answered.
[HTC Amaze 4G] Dark Nightmare:
Did you even look at the link I posted in your thread? If you did, then you wouldn't be looking to put the sound file in the bootanimation, but instead put it in the required folder, that's why I linked to a tutorial, it is there for a reason.
[Samsung Galaxy Nexus] sarveshvaity:
I was looking at the Specifications and the US Version does not list 900 Mhz in 3g radio.

From play.google.com

NETWORK

GSM/EDGE/GPRS (850, 900, 1800, 1900 MHz)

3G (850, 1700, 1900, 2100 MHz)

HSPA+ 21

When i bought I9250, the specifications listed were:

Connectivity

Wireless Radio

GSM 850 / 900 / 1800 / 1900 MHz

UMTS 850 / 900 / 1700 / 1900 / 2100 MHz

So, are US Version and Internation Version same Hardware or is the US version really missing the 900 Mhz UMTS radio?

- Sarvesh
[Samsung Galaxy Nexus] shadow65781:
Everyone says it's a typo that it should be the same. Lots of people asking that

Don't bait the trolls.
[Samsung Galaxy Nexus] babymatteo:
+1. Yup just a typo.
[Samsung Galaxy Nexus] sarveshvaity:
Thanks
[Samsung Galaxy Nexus] propain4444:
On a somewhat related subject.

I'm about to buy a gnex, i can either go for the $399 deal from google's site, or i can get the i9250 from Amazon. If i go the Amazon route i'll actually save quite a bit of cash thanks to gift cards and the lack of tax/shipping charges. So here's my question.

I've read a lot of information about the i9250 imports and warranty issues in the US (i.e. warranty is not honored in the US). Is the model number the same now that the unlocked version is being sold state side, and does anyone know if Samsung US will now warrant the i9250s?
[Samsung Galaxy Nexus] greeced:
I don't see how they can't... Samsung should warranty their product worldwide... Its still their product, no matter where you bought it from.

But to be on the safe-side, I would contact Samsung USA and inquire with them......

Afterall, you'll get many answers here... some saying yes, some saying no... but none as definitive as the horses mouth.
[Samsung Galaxy Nexus] propain4444:
Good idea... i had never thought about contacting them directly.
[Samsung Galaxy Nexus] aldo37:
Incorrect. They do not warranty their products worldwide and the international versions (before selling in the Play store) were imported and considered grey market items (and they absolutely do not warranty grey market items). Almost all companies don't.

That said, I'm not sure on the status now that it's being sold in the U.S. via the Play store. I am sure they will have you verify purchase from the Play store or something similar for warranty service.
[Samsung Galaxy Nexus] propain4444:
So, does this mean, now that it's for sale in the play store, i can buy the i9250 from Amazon without concerns of warranty? (or, i should still contact samsung)
[Samsung Galaxy Nexus] aldo37:
I'm not sure on this. They may have you verify the purchase from the actual Play store itself somehow.
[Samsung Galaxy Nexus] propain4444:
I just talked to Samsung. The model numbers are the same (i9250) for both international and domestic phones, however Samsung USA keeps separate records for both. So, in the case of the int'l version you would not be able to get warranty service through Samsung USA. However the rep said:

"You would have to file an international warranty claim, and i have never heard of a claim not being honored."

Granted he's just a front line rep, but that is promising information.

I guess really this is all a moot point, since regardless of how hard i try i will have the phone rooted within 3 months. I really do want to resist voiding the warranty early on this phone... but i don't see myself holding out for very long.
[Samsung Galaxy Nexus] greeced:
No one ever said anything about a grey market item. With all due respect, buying a product internationally and bringing it here does not constitute 'grey market' as you put it. If it does, I would like to know a source for your information.

Secondly, I've purchased a Samsung TV in the states before, and had to get it warrantied here in Canada. They knew the set was bought in the U.S., but still warrantied it here.

So by your thinking, they warrantied a grey market item. Hmm...

And as the previous poster said, they must have filed an international claim... either way, I got my set fixed.
[Samsung Galaxy Nexus] ChongoDroid:
My international was bought on eBay, warranty is void.
[Samsung Galaxy Nexus] greeced:
As far as I'm aware, as long as you bought it from an Authorized Samsung Dealer, its warrantiable anywhere.

eBay sellers I guess can't be verified.

EDIT: We can even go as far as saying they would warranty anything without proof of purchase, provided that the manufactured date falls within the 1 year. I know they were doing that with a bunch of original Galaxy S's way back when they had issues. At least the service centre in Montreal was from my recollection.
[Samsung Galaxy Nexus] tvdang7:
i am in the same boat i have like 300 in gift cards i dont know what to do!!!:confused:
[Samsung Galaxy Nexus] aldo37:
Do you know what grey market means? Read up: http://en.wikipedia.org/wiki/Grey_market

The GSM GNex (before selling in the Play store) was never officially for sale in the U.S. and stores imported it from other regions and sold it here in the U.S. That is the definition of grey market.

TVs may be different for Samsung, so who knows. Go ahead and do a search of the many, many, many threads asking and noting that there was no warranty from Samsung regarding the GNex bought from overseas in the U.S.

And I wouldn't trust any sort of first line customer service rep about international warranty. If that was the case that information would be *everywhere*.
[Samsung Galaxy Nexus] propain4444:
I ended up buying from Amazon... It's actually cheaper than getting from the play store even if you don't have gift cards because of the lack of tax and free shipping.
[Samsung Galaxy Nexus] greeced:
Somehow I knew Wiki was going to show up in your reply.

Fact is, prior to them selling the GSM version here, then yes you can classify it as such... Now that they sell it here, it's no longer grey market. So you can service your model here no problem.

And as for TVs it would be the exact same thing... Model I bought was purchased in the U.S., but also sold in Canada... so there is many logistics as to why they would service it no problem as opposed to buying a model that wasn't sold here (parts, know how, etc)...

That doesn't apply anymore, because the 9250 is truly international now. So again, its no longer grey market, no matter how long ago you bought it.

So I "Read Up" as you put it... but your definition doesn't hold water if you "Read between the lines".

Last edit: And for your information and to be clear - grey market refers to product being sold outside of a manufacturers authorized distribution demographic. Nothing more, nothing less. For example.. anyone remember DirecTV way back? How Canadians were importing them and using them here? Thats grey market because DirecTV never had any intention of distributing them here.

Those demographics have changed for Samsung, and if you're not going to trust a customer service rep who's telling you the same thing, then I guess we should all just believe you.
[Xperia Arc Q&A, Help & Troubleshooting] davibs:
Hi guys!

I noticed that using CyanogenMod, the LED notification is much more powerful than the stock.

I love this feature as I can take on a different rom?

How to increase the power of the LED to the max?

Thanks for your help ..!

(I am using JJ's Rom Arc-Night Kernel)
[XPERIA X10 Android Development] darksherko:
remember to hit thanks if you enjoyed the rom and i helped you out! :D​

Darksherko industries 2012​
[XPERIA X10 Android Development] ilamaan:
why was the cm9 deleted actually?
[XPERIA X10 Android Development] darksherko:
yes it was :(
[XPERIA X10 Android Development] muratbaizhanov:
screenshots please to see the difference
[XPERIA X10 Android Development] Riddo:
Hi,

Is it for locked or unlocked BL, or for both ?

What are the main differences from FXP CM7 ?

Cheers
[XPERIA X10 Android Development] darksherko:
screenshots not needed yet mate just wait a few days for RC2
[XPERIA X10 Android Development] darksherko:
locked bl

bb 71 needed

main difference is some apps and others i dropped in the rom

not that much difference just wait for RC2

more to come then!:D
[XPERIA X10 Android Development] maikinho10:
Locked bootloader NEVER if you use cm 7.2 kernel!

..and this rom is the same like "your" cm9 rom..no difference to great famous FXP ROM!!

Why do you release roms, if the difference =zero :what: :confused:

Greets Maik

EDIT: and i think camcorder lags right;-)?

Gesendet von meinem GT-I9100 mit Tapatalk
[XPERIA X10 Android Development] smithinsundar:
When someone comesup with something pls dont discourage ....maybe he gmhas developed it for personal use n might have shared it out f generosity ....if u dont like it ...just ignore it...as simple as tat

sEnT fRoM SoMeThiNg wHiCh wAs SuPPosEd tO bE aN XpeRiA X10....