Database Users

2.2\I9000XXJPY broke my sms app

is there a solution other than reflashing with another build? my sms app crashes - third party app too, seems the android-function is broken or wasnt updated. wiped both sd-cards, no change..
thx!

Do you get any error message?

yes, when opening the sms-app: sorry! the apllication messages (process com.android.mms) was stopped unexpectedly. try again (in german).

did you do a factory reset?
did you remove any apps from system?

can it be because i used pit: s1_odin_20100803 ?
which one to use? i also flashed without a phone or csc, as i couldnt find the corresponding ones. are these needed? i thought no..

yes those the csc is needed..
also that is the incorrect pit.
you should reflash a complete firmare ie jpo jpu with 512 pit..
then relfash entire jpy wit csc, modem everything and dont use a pit.

thanks, but on these list which csc matches which firmware? i cant seem to find a corresponding csc to the european firmwares:
http://forum.xda-developers.com/showthread.php?t=846913
thx

you are misunderstanding those are entire firmwares that come with the csc and modem in most cases you dont need a separate csc.
here is the direct lins
http://www.samfirmware.com/apps/auth/login?why=pw&try=1&wp=1&next=WEBPROTECT-i9000.htm

it's only a .pit problem. You need to reflash with 512 .pit. check for a full rom like jpu and with re-partition use 512.pit. After upgrade to jpy.

thx, flashing with 3 files from the jp1 package resolved the problem!

[Q] Can't Flash Back To Stock

i have the international i9500 and i wanted to flash stock firmware to remove the bloatware and i tried to flash the stock rom with the adonis.pit and i checked re-partition .
when the flash was finished the bloatware wasn't removed and the boot anmation didn't revert back to the samsung animation and the phone also remembered my wi-fi password considering the fact i re partiotioned and wiped data.
how can i flash a stock rom without the bloatware (i'm from israel)
on sammobile there was the following options:
israel (cellcom)
israel (orange)
and israel (ILO) which is the stock one without the bloatware and when i flashed it the bloatware wasn't removed

Flash a stock firmware without PIT and without repartition.
Then use TrulyClean script to remove all the bloatware.

ignaciojn said:
Flash a stock firmware without PIT and without repartition.
Then use TrulyClean script to remove all the bloatware.
Click to expand...
Click to collapse
i flashed again without pit and without pepartition but the boot animation is still the carrier boot animation and not the samsung one as it should be.
will the trulyclean script restore the regular samsung boot animation?
oh and even after i reflashed without the pit and without the repartition it still remembered my wi-fi pass?! how do you explain that?
let me explain with a more basic explanation:
i bought the phone and the current rom was the cellcom branded rom (one of our carriers)
so i jumped to samfirmware and downloaded the israel/ILO which is an unbranded one
and flashed it the way you said (w/o pit and w/o re-partition) but the bloatware was still installed even after i did a factory wipe.
HOW COULD IT BEEE????

LSGio said:
i flashed again without pit and without pepartition but the boot animation is still the carrier boot animation and not the samsung one as it should be.
will the trulyclean script restore the regular samsung boot animation?
oh and even after i reflashed without the pit and without the repartition it still remembered my wi-fi pass?! how do you explain that?
let me explain with a more basic explanation:
i bought the phone and the current rom was the cellcom branded rom (one of our carriers)
so i jumped to samfirmware and downloaded the israel/ILO which is an unbranded one
and flashed it the way you said (w/o pit and w/o re-partition) but the bloatware was still installed even after i did a factory wipe.
HOW COULD IT BEEE????
Click to expand...
Click to collapse
NVM problem Solved

you should also tell the solution, and mark the thread as solved. this way, other users can solve the problem without opening a new thread

okty2k said:
you should also tell the solution, and mark the thread as solved. this way, other users can solve the problem without opening a new thread
Click to expand...
Click to collapse
Ok so there was an error in sammobile servers and the ILO firmware and the cellcom one are the same so that's why i had all the cellcom bloatware
and can you please tell me how to mark the thread as solved?

[Q] Soft Bricked Note 3 When Attempting to Flash Stock 4.4.2 Firmware

I have a Note 3 SM-N9005. There was a polish release of 4.4.2 firmware, which I'm fairly certain was this, which I installed in January using this guide on XDA.
Today I discovered that my carrier (Telstra, Australia) had released an official 4.4.2 firmware N9005XXUENE3, and thought I would flash it. The flash failed and I got the message "Firmware upgrade encountered an issue" in recovery. In a panic, I tried to return to the polish firmware. Having lost what I'd originally flashed, I tried N9005XXUENA6 from sammobile first. This got me to the setup screen, but the phone would crash on the first or second page of setup with "Unfortunately Samsung Setup Wizard has stopped". I then downloaded the N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX from the first link. This has the same result.
After each flash I did a factory reset and wiped the cache (not dalvik, because I'm not rooted). The stock firmware comes just in the form of a .tar.md5 as did the N9005XXUENA6 from sammobile, but the final polish firmware and the original I had installed had separate parts for bl, ap, cp, csc.
Is this what it means to be soft-bricked?
What was the mistake that I made to result in a soft brick?
What can I do to have a functional phone again, either with stock firmware or anything at all?
Given that my knox is still 0x0, is it likely my warranty is void anyway, and can I repair this somehow?

Go to SAMMOBILE and download the latest Polish or Slovakian rom using the europpean pit. My N9005 is polish too, and yesterday I had the same problem, thinking that since I am bulgarian , the bulgarian rom should work.
So install the Polish or Slovakian (see down) and it should work...
+ this pit: http://forum.xda-developers.com/attachment.php?attachmentid=2427062&d=1385931899
SM-N9005
Poland (T-mobile)
2014 October
4.4.2
N9005XXUGNI4
N9005TPLGNI1
or
SM-N9005
Slovakia
2014 October
4.4.2
N9005XXUGNI4
N9005TMSGNI1
Alexander_Q said:
I have a Note 3 SM-N9005. There was a polish release of 4.4.2 firmware, which I'm fairly certain was this, which I installed in January using this guide on XDA.
Today I discovered that my carrier (Telstra, Australia) had released an official 4.4.2 firmware N9005XXUENE3, and thought I would flash it. The flash failed and I got the message "Firmware upgrade encountered an issue" in recovery. In a panic, I tried to return to the polish firmware. Having lost what I'd originally flashed, I tried N9005XXUENA6 from sammobile first. This got me to the setup screen, but the phone would crash on the first or second page of setup with "Unfortunately Samsung Setup Wizard has stopped". I then downloaded the N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX from the first link. This has the same result.
After each flash I did a factory reset and wiped the cache (not dalvik, because I'm not rooted). The stock firmware comes just in the form of a .tar.md5 as did the N9005XXUENA6 from sammobile, but the final polish firmware and the original I had installed had separate parts for bl, ap, cp, csc.
Is this what it means to be soft-bricked?
What was the mistake that I made to result in a soft brick?
What can I do to have a functional phone again, either with stock firmware or anything at all?
Given that my knox is still 0x0, is it likely my warranty is void anyway, and can I repair this somehow?
Click to expand...
Click to collapse

My note 3 is not actually polish. I used the polish firmware because it was the first to offer 4.4.2. Does this suggestion still apply?

Alexander_Q said:
My note 3 is not actually polish. I used the polish firmware because it was the first to offer 4.4.2. Does this suggestion still apply?
Click to expand...
Click to collapse
I'm not sure... do you know your original configuration, before this 4 file polish rom?
Still you need to try and flash, one thing is sure, you can't flash an older one. So if your phone is not locked to any operator than any latest stock rom from your region should work. If you're not sure which region is your phone originally from, then there's a problem....
So go to sammobile, type n9005 in the firmware tab, and try the ones at top,October...November, from your region. And use the pit file too.

The latest for my region and carrier is N9005XXUENE3, which is what got me into trouble in the first place in my OP. What should I try next?

Update: Got past setup and into homescreen. Usually crashes after about 10 minutes, but sometimes I can get up to a few hours. Doesn't detect the SIM card, and camera doesn't work. Any clue what might be going on?

Alexander_Q said:
Update: Got past setup and into homescreen. Usually crashes after about 10 minutes, but sometimes I can get up to a few hours. Doesn't detect the SIM card, and camera doesn't work. Any clue what might be going on?
Click to expand...
Click to collapse
http://www.sammobile.com/forum/showthread.php?t=20032
do this above
load your rom in the AP
load the pit File
use odin 3.0.9
good luck
I did the same and it worked

G900F O2 de-branding

Hello pros,
I have a S5 (G900F), bought in Germany that has a provider branding from O2 (VIA) I want to get rid off.
After searching and reading many many many threads I wasn't able to find as "safe" solution. There are some threads, where people were able to flash a stock firmware, but it was BTU. Some managed to flash the DBT, but with errors during procedure, workarounds etc.
Since the key to flash from VIA firmware to another seems always to be the correct PIT file and the PIT files also seem to come from this forum I hope to get some professional help to solve my problem. I've already read enough contradictory statements from people who think they might know something, but I'm looking not for assumption.
Here is data from my S5:
AP: G900FXXU1ANG2
CP: G900FXXU1ANG2
CSC: G900FVIA1ANG1
So I have Android 4.4.2 and would like to flash a 5.0 DBT and to keep the KNOX of course.
1. First I wondering why it not working to flash the DBT fw on a VIA S5 with the "original" DBT PIT? If the VIA phones have a different partition layout the PIT for DBT should solve this or not?
2. The most promising solution seems to be use the DBT (it's not state from which to which version the update was done) with special pit version for s5 (also not clear which one was used). When flashing with Odin at the end always a failure message will be displayed. Then disconnect and reconnect the phone and to flash only the PIT after a restart to wipe all. But as mentioned earlier that doesn't sound like a "safe or proven" solution.
Here is the link-> (German) handy-faq.de/forum/galaxy_s5_original_roms_firmware_kies/306126-samsung_galaxy_s5_branding_entfernen_sm_g900f-18.html#post2926313
3. Suppose I use the solution as described in 2. and flash the first 5.0 version (...BNL9) and then perform a update using the build in updated function on my S5 (no Odin, Kies, etc. ) to the second 5.0 version (...BOB7) will the update clean up the possible mess I've done using the procedure above? Or would it be better to use the Kies software on PC to update from 5.0 to 5.0?
I really appreciate competent help on this (and probably many other in the same situation) and no abuse of this thread for other topics .
As step by step guide with a link to PIT file and tool version info (Odin 3.09 etc.) is very welcome.
Cheers!

Flashing the DBT over an o2 branded device is ok. The upcoming error in the end, related to a to small cache.img ext4 partition comes up because of the comparsion by odin of the is and the has to be partition size.
At this stage the DBT rom at the S5 is not installed, it's like a download only. If you now flash the right *.pit as a next step this will adjust the partition size. The installation afterwards will be work and all is on a clean state. Have done this yesterday here in Germany using before o2 branded S5.
Sent from my SM-G900F using XDA Free mobile app

Thank you for the quick reply Endur.
Is there a guide I can follow for the whole procedure (what you did on you phone)? And where can I get the "right" PIT file?
I had some experience flashing a Galaxy S1, so I know this might be tricky and would like to avoid any possible heart attacks during the procedure .
Thanks in advance.

Flash bob7 DBT using Odin (I have used 3.10).
After that you will get the failed message because of wrong partition size.
Unplug USB cable.
Plug USB cable.
Flash *.pit (European for G900F 16GB)
You will get a note now about adjusted partions. The installation of bob7 DBT will start now (you see the green Android spinning). You may wipe cache and data as last step.
Sent from my SM-G900F using XDA Free mobile app

Alright, with mental support of Endur and some courage I just de-branded my phone by updating it from VIA (O2) 4.4.2 (G900FXXU1ANG2) to no branding (DBT) 5.0 (G900FXXU1BOB7). I've used Odin 3.10 and Samsung USB Driver for Mobile Phones 1.5.51.0.
The flashing procedure is basically as described in many other posts, so I don't want to create a copy of a copy. Please take a look for yourself.
Instead I will only add the steps required for O2/VIA de-branding with my experience.
As Endur mentioned the first step with Odin doesn't flash but "copy" the firmware to the phone. Due to different partition layout Odin will show an error. Remove the USB cable and replug it while Odin is still running. Remove the check from "AP" (former PDA) in Odin, select correct PIT, check "Re-Partition" in Odin and press "Start". Now comes the excitement moment. My phone got stack showing Android, powered by Google etc. I had to remove the battery, boot into recovery an wipe data and cache. So it seems to be a must instead of may.
I've used the SM-G900F_pit_16GB.zip (for German / DBT version) from forum.xda-developers.com/showthread.php?t=2737448
Good luck!

Yes, wipe data and cache is a good idea while updating from Android 4.2 up to 5.
There is a lot different for data, Dalvik was changed to ART and much, much more.
I had updated from BTU BNL9 to DBT BOB7 only. The DBT requires the greater partition size for hidden.img while BTU can be flashed without any partition change to a formerly German o2 branded device.
Sent from my SM-G900F using XDA Free mobile app

Galaxy S5 SM-G900F change HK firmware to UK BTU

Hi,
I purchased a Galaxy s5 (SM-G900f) from an ebay seller which came in a sealed box as described. Unfortunately it arrived with non UK firmware which the seller "forgot" to mention and has since confirmed it to be from HK.
I am pretty sure it is a genuine G900f and not a fake, and would like to know if/how this can be updated to a UK BTU firmware.
Current firmware is
AP : G900FZHU1AND1
CP : G900FZHU1ANCD
CSC : G900FZZH1AND1
Ideally I would prefer to update to android v5 rather than v6 from the current v4.4.2
With this is mind I downloaded G900FXXU1BOI3 as a single tar file.
From reading around a bit, I am unclear whether I need a separate CSC file for changing the modem, or whether any additional checkboxes need to be enabled from the default ones on Odin.
I read somewhere that dialling the following code with your device IMEI number: *#272*IMEI Here# will list available ones to choose from - but will I get the BTU option by flashing the firmware listed above?
Any advice would be greatly appreciated.
Thanks

Still seeking clarification on whether I need a separate CSC tar.md5 or not.
Also should I keep my UK sim in the phone so that when I delete cache and factory reset, the BTU CSC will be selected?
Thanks

OK - decided to risk it after a bit more searching as wasn't sure when I might get someone able to confirm things.
I used the firmware listed above (single tar file).
Ensured my UK Sim was in the phone
Made sure Odin "Re-Partition” and “Auto Reboot” were not enabled
And ran the update. All worked OK and my CSC is now the correct UK one.
Was expecting to need a “Wipe data/Factory reset” but this didn't prove necessary.
Hope this helps someone else in the future.

Hi guy!
I have the same firmware G900FZHU1AND1
where to get the tar file?
Thanks in advance.
snissim said:
OK - decided to risk it after a bit more searching as wasn't sure when I might get someone able to confirm things.
I used the firmware listed above (single tar file).
Ensured my UK Sim was in the phone
Made sure Odin "Re-Partition” and “Auto Reboot” were not enabled
And ran the update. All worked OK and my CSC is now the correct UK one.
Was expecting to need a “Wipe data/Factory reset” but this didn't prove necessary.
Hope this helps someone else in the future.
Click to expand...
Click to collapse

Hi, I don't remember for sure, but I suspect it was from sammobile.com