Hello friends
Have a question
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update
No, you can't do that. This will brick your phone..
Wait for your regional update..
sharingan said:
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update
Click to expand...
Click to collapse
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.
fffft said:
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.
Click to expand...
Click to collapse
Okk then
I will wait for my update
I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
fffft said:
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone
Click to expand...
Click to collapse
drakester09 said:
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.
fffft said:
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.
Click to expand...
Click to collapse
The condescending tone of yours is ill fitted to this conversation.
I read your post, now could you be so kind to actually read mine?
What issues did you guys have when flashing a different region firmware?
Click to expand...
Click to collapse
Can you please share some cases where this has happened?
Where it has been stated and proven that CSC differences can risk your phone?
If so then the CSC changer app is a risk and should be removed, but it isn't.
We are not talking about variants, of course T/L/S/F are not the same despite haviing Snapdragon and you might break something when cross flashing, basebands are different, etc etc.
All G900Hs are equal. The software that was built for one G900H will work in another.
The carrier/regional customizations COULD cause issues if there's a certain incompatibility between app data, but they are easily fixed by a wipe.
For once the PIT argument is useless, Odin pulls the current PIT from your phone to map partitions.
In old days the update was not as seamless and you might be forced to use a PIT file. That's not the case for current releases.
drakester09 said:
The condescending tone of yours is ill fitted to this conversation.
Click to expand...
Click to collapse
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.
fffft said:
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.
Click to expand...
Click to collapse
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.
gee2012 said:
Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
Lets agree to disagree. Imo you don`t have to flash a pit file if you flash a compatible rom for your model with the same partition layout (16 or 32GB) everytime you flash a stock rom.
PS saw earlier posts by you and i want to point out none of my my advices/posts ever lead to a bricked device
fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
I'm sorry to be a bother but could you please share any case where the mentioned situation has happened?
There must be at least one or several.
I'm all in for factual data so I'd love to see real scenarios where this has happened. It will take you much less time than to post such a long winded post and will prove your point.
Thanks in advance.
gee2012 said:
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
drakester09 said:
I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
Sent from 5th Galaxy
How did you cross flash i got G900P i want to flash G900WD how ?
Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.
waleed794 said:
Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.
Click to expand...
Click to collapse
Im have the same problem!
Im have a S5 SM-G900M and try install G900F and have the same error.
Is possible install this?
Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app
sandeep20064096 said:
Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app
Click to expand...
Click to collapse
Hi.
Im think your phone have a different chip
For example the difference into g900m and the g900f is the bands avaible
The g900m have only 900Mhz / 1800Mhz
The g900f have all bands
But in try install the firmware g900f into g900m but dont work.
please help
walkermoon said:
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
Sent from 5th Galaxy
Click to expand...
Click to collapse
i want to flash newest cambodia ROM to my S5 g900h ... so can i do it easily with odin or i want to change moedm firmware and bootloader first ?? and please help me ASAP
i rooted my S5 and i flash the recovery. but now it has error that it could not run cache partition ...
so i want to go back to stock ... tell me if i have to go to direct cambodia ROM or i have to flash india ROM first ??
please help me with this
Related
Hi, I have recently bought a Samsung GS2 from China and the kernel that comes with it is KG5. I wanted to flash the phone with firmwares from other country but I'm experiencing so many problems during the process. I use odin 1.85 and the official firmware downloaded from samfirmware.com but everytimne I try to flash I get the following error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKG3_CL401405_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG3_REV_02_CL1040774.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKG3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The only other times that I were able to succeed is when I flash with the original CSC = OZHKG5 firmware that was meant for China region. Is there something that I did wrong? Am I not supposed to flash firmwares from a different region? Am I pretty much stuck with the China firmware now? Thanks!
Can anyone help? I'm really stumped on this.
Flashing other region rom should be no problem..
did u flash the rom correctly.. follow the instruction..
try flash the phone using other rom..
yes, i followed the instruction on using odin carefully. i also tried other roms but i still get the same problem.
I'm experiencing the same problem...
god, I should never have taken my dad's chinese sgs 2, assuring him that I will install a rom that is better than the original stock firmware...
hi
I had this problem 2, it should be no problem to flash another firmware. Please retry the flashing process using another original sgs cable, tell me how it goes
Dudes the Chinese model, not Hong Kong one, cannot work with the normal firmware for the international version. It will not flash. I believe they had to make some changes to it before they were allowed to sell it in China.
make sure that any process named starting with kies* is killed from windows task manager.
i recollect facing the same issue when flashing a ROM (my phone is not from CHINA to make the point that its not device specific)
i m in same situation : restrained into the chinese version of znkg5. it is so mich localized and stipped with its applications installed that it can hardly br condidered android anymore. and for sure it is not "open".
i tryed manu many rom via odin, failed all and came back to znkg5. the procedure via odin is not the issue as i can flash the znkg5 properly. it is either the rom or the hardware itself.
did someone tried some flash in world glock mode (via sd card) ?
do u know anothet forum about this flash, even in chinese ?
Same
I'm facing the same problem...
now I can't boot the phone, and access the recovery mode... only download mode(hope this is good).
when try to boot the phone, the android robot appear in red, and a message "system update fail" and something in chinese.
Note: I got this phone as a gift, and was bought in China, but actually I'm not in China, I'm in Brazil...
Is this the case to take to an authorized samsung technical service and hope they can solve this? or there's any other hope?
Thanks
You're good, Download mode is all you need. As Intratech said, the only way to get it working is to flash it with a China based ROM.
http://forum.xda-developers.com/showthread.php?t=1192575
I hope you speak Chinese... well it does have English locale on it.
It's proved that I9100 sold in China could not flash original international firmware.
If you insist to use a international firmware on it, remove boot.bin, modem.bin, param.lfs and Sbl.bin from the firmware tar file, and then have a try.
And you may use Clockwork Mod to flash baseband.
delete
10 char
What about me installing the China version on my Taiwanese hardware? I've read that Google is removed and Baidu becomes default etc. Sounds like a nightmare, but I really want Chinese KB support AND 2.3.4.
downwiththebanksters said:
What about me installing the China version on my Taiwanese hardware? I've read that Google is removed and Baidu becomes default etc. Sounds like a nightmare, but I really want Chinese KB support AND 2.3.4.
Click to expand...
Click to collapse
surely there are app for chinese keyboards that you can use? The only thing that cannot be chinese are the menus, as far as I know.
hua_wuxin said:
It's proved that I9100 sold in China could not flash original international firmware.
If you insist to use a international firmware on it, remove boot.bin, modem.bin, param.lfs and Sbl.bin from the firmware tar file, and then have a try.
And you may use Clockwork Mod to flash baseband.
Click to expand...
Click to collapse
Has anyone actually tried this? I keep hearing there's a signed bootloaded on these Chinese phones. How does one verify this without trying to load a different one and (potentially) hardbricking the phone?
lobo1976 said:
surely there are app for chinese keyboards that you can use? The only thing that cannot be chinese are the menus, as far as I know.
Click to expand...
Click to collapse
Nearly 70% of all android malware originates from china, so I'm loath to download anything chinese in origin. Yes I know that is a bit of a contradiction for my goal.....just because you're paranoid doesn't mean they're not watching.
Here are some 2.3.4 roms (LeoMar75, Villain, Cognition) with the Samsung Chinese keyboard included: http://www.mobile01.com/topicdetail.php?f=568&t=2188818&last=30763131 (Note: I have not tried any of these.)
I use Cognition 1.5.1 on my Taiwan phone. I don't have the Chinese keyboard with the new firmware. Maybe I will try to re-add it later, but my Chinese is poor so Google Pinyin IME is enough for me.
I need to have BPMF for my wife/kids/other sundry locals to use the phone mostly to input GPS. As you know, most locals can't pinyin, BPMF is their standard. Does the above google pinyin IME have BPMF, or is there a BPMF. Truth be told I don't even know what the acronym IME means.
You can use chinese firmware only
:crying::crying::crying: I can`t flash my S4 SGH-M919V with odin, i try to flash any firmware lollipop 5.0.1 of GT-I9505 that is the same thing and others firmwares of 4.4.4 of the same model but always send me FAIL abort the operation.
I don`t know why when I put my s4 in odin mode show this information in small letters:
ODIN MODE
PRODUCT NAME: SGH-M919V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
MMC BURTS MODE: Enabled
One question the last lines maybe is the problem write protection enabled or not? if is yes the problem how i can fix it for flash any firmware on my s4 thanks for your time (if this post is in the wrong section please change thanks again) i hope solutions XDA-Developers
http://forum.xda-developers.com/galaxy-s4-tmobile is where you need to go for issues with your device, as that forum has far more people familiar with your S4. This is the international S4 forum.
Now, regarding Odin, you should be using a recent version of Odin (current is 3.10), the original cable connected directly to the computer, not using a hub, and not have Kies running. You may also need Samsung's drivers if you haven't installed Kies or downloaded them from Samsung, so if you haven't already downloaded them, do so. That said, attempting to flash an I9505 ROM to your device is automatically going to fail. Odin verifies the model number and other parameters in the S4 before it allows a flash to proceed. Naturally, the model numbers don't match and thus flashing the ROM will not work.
Write protection and MMC bursts modes are supposed to be enabled, so you can eliminate that as a concern.
Thanks for your anwer bro but so to try install a firmware of the same model of mine and the same error
Post your Odin log, so we can see where it fails.
This is mi phone information: i have install Albe95 rom
AP:I9505XXUHOA7
CP:M919VVLUFNH3
CSC:I9505OXAHOA7
This is the Error with any versión of odin and any firmware stock forma this model or :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUHOB7_I9505YXYHOB5_I9505XXUHOB7_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:17)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Any solution? Thank s
I read some post and say it that write protection is enable never can't flash any firm help
Seriously? After telling you that you cannot install an I9505 ROM on your device and explaining why you can't, you're still trying?
YOU CANNOT INSTALL AN I9505 ROM ON A T-MOBILE S4! All attempts to do so will automatically fail. The only stock ROMs that will work on your device are T-Mobile ROMs.
What part of the above do you not understand? Tell me now so I can dumb things down.
i m understand all above OK
this log show with any firmware for the phone or t-mobile firmware men i triying to install stock firmwares for my mobile ok and don`t work of any way but thanks for your time and help :good::good::good: i waiting for more solutions or i read the link than you put above
@LE_17: I apologize for snapping. However I thought I had made it reasonably clear that you could not install an I9505 ROM on your device. Apparently this wasn't the case. In any event, your ROM is here.
that s ok bro no problem
thank s for your time but the link of the firmware that you post i have in my PC downloaded and when i flash it send the same error i dont know why :crying::crying::crying:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Strephon Alkhalikoi said:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Click to expand...
Click to collapse
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Try to flash the latest version from here.
http://www.sammobile.com/firmwares/database/SGH-M919V/#firmware
if it fails, try different usb port and different usb cable.
Try using the latest version of Odin (v3.10.6) and see if you can flash the correct firmware for your rom.
http://forum.xda-developers.com/showthread.php?t=2711451
Try using a different USB port if its failing again and make sure your USB drivers are up to date
Ok man i try it thanks for your time and answer post the result
Lennyz1988 said:
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Click to expand...
Click to collapse
Well color me silly. I did miss that, and I'm sure the OP did too as he mentioned already having that ROM.
LE_17 said:
Ok man i try it thanks for your time and answer post the result
Click to expand...
Click to collapse
If you're trying to flash the official Lollipop update for the S4, use the Canadian version. I tried using the Rogers version (as Videotron uses Rogers' network) from SamMobile and it worked perfectly well. I was even able to change my CSC to Rogers and get the update through Kies.
Disclaimer: If you choose to try this, it is at your own risks. I cannot be held responsible if your phone gets damaged in any way nor can I guarantee the results.
No need for this anymore! The SGHM919V has gotten the Lollipop update this morning.
All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.
Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?
Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.
It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.
You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.
Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-
100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.
I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.
@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.
Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.
Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.
Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:
eranda84 said:
Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:
Click to expand...
Click to collapse
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin
4Smoky said:
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin
Click to expand...
Click to collapse
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?
eranda84 said:
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?
Click to expand...
Click to collapse
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )
popmpopm said:
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )
Click to expand...
Click to collapse
if you don't mind can you get me steps? Which region pt file? (KLTE_EURO_OPEN?)
No help?
Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust
*Detection* said:
Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust
Click to expand...
Click to collapse
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:
if anyone can help me i'll help him / her to buy a beer
Use Kies 3
eranda84 said:
if anyone can help me i'll help him / her to buy a beer
Click to expand...
Click to collapse
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.
eranda84 said:
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:
Click to expand...
Click to collapse
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is
*Detection* said:
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is
Click to expand...
Click to collapse
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
heisenberg281 said:
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.
Click to expand...
Click to collapse
Hey man, this is pretty cool until it's started installed to mobile, but it's not continue. Because below error message appeared on mobile with red letters.
"secure check fail : pit" what should I do now? Please need assistance. :good:
keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
@ *keithross39* hey sir, please help me on this.... :crying::crying::crying:
There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
1) Yes. That's pretty sure me too.
2) Not a H variant
3) Yes.
As I mentioned first post there's two IMEI numbers. But none of those not similar to sticker under battery compartment. (Not match with any of those)
I have rooted mobile using "CF-Auto-Root-klte-klteduosxx-smg900fd". And it's successfully rooted.
And I did IMEI/EFS backup using "Samsung Tool". Now what should I do as a next step?
First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ok thank you sir and Hats off. :good:
Have a Good Night
I have tried everything but again failed in Re-partition. Now only one left. That's run a custom rom. Will see CM13 and back to stock rom.
But anyone can help me on pit file failed, please help me.
keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Never to date have we seen or heard of download mode being wrong, and CF AR for the G900FD just worked for OP
And if it turns out to be wrong, we both have a LOT of threads to edit when we have told other members to always trust download mode
To my knowledge, there is no way to reprogram the chip on the board to change the model number in download mode, maybe the phone is a fake
@ OP - can you post a photo of the back of the phone, with the back cover removed, so we can see the physical location of the SIM slot?
Edit out the IMEI etc if it shows on a sticker
Hi guys, looking for a little help / advice.
I have a UK Galaxy S4 (I9505) which is rooted and running CM12.01 ROM.
I am trying to Unroot and restore a stock rom via Odin, but it always fails.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of the firmware, different versions of Odin. Changed USB cables and ports, but always the same error. Any advice greatly appreciated.
Thanks
Are you flashing the newest firmware available?
GDReaper said:
Are you flashing the newest firmware available?
Click to expand...
Click to collapse
I think so....
the file is: I9505XXUHOD7_I9505EVRHOD1_I9505XXUHOD7_HOME.tar.md5
flashing original rom for samobile.
johnfree98 said:
flashing original rom for samobile.
Click to expand...
Click to collapse
that is originlal ROM from sammobile as far as I know.
the version bootloader and modem to be the same that gives you the cm
johnfree98 said:
the version bootloader and modem to be the same that gives you the cm
Click to expand...
Click to collapse
not quite sure what u mean, could you explain please...
mrmcox said:
not quite sure what u mean, could you explain please...
Click to expand...
Click to collapse
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.
GDReaper said:
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.
Click to expand...
Click to collapse
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...
mrmcox said:
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...
Click to expand...
Click to collapse
The one with the same baseband. It's worth a try.
GDReaper said:
The one with the same baseband. It's worth a try.
Click to expand...
Click to collapse
Ok, I've found a Stock ROM with the same baseband, but its a US Sprint based ROM, and I have a UK based phone....Will this be ok ?
No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.
Strephon Alkhalikoi said:
No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.
Click to expand...
Click to collapse
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again
mrmcox said:
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again
Click to expand...
Click to collapse
The "about device" info can be changed very easily. You could make it show that your device is a S7 and is running iOS.
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T
And since it's a Sprint phone, there is one major thing to keep in mind. In the UK and on the European continent, that phone will not get LTE service. The radio in the phone expects to see American channels and won't pick up the European ones. This is like my S4, but only in reverse. In my case, my S4 expects European channels as it's an I9505 and doesn't see American channels.
The only exception to the above is if the original owner managed to rewrite the Qualcomm chip to enable European bands.
GDReaper said:
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T
Click to expand...
Click to collapse
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?
mrmcox said:
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?
Click to expand...
Click to collapse
It used to say GT-I9505 in download mode?
GDReaper said:
It used to say GT-I9505 in download mode?
Click to expand...
Click to collapse
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?
mrmcox said:
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?
Click to expand...
Click to collapse
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.
GDReaper said:
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.
Click to expand...
Click to collapse
Is there any way to try and convert it to I9505 baseband, as now it wont receive any data signal in uk, which it always did before. if so how can I do this, and what files should I be looking for ?
thanks