Database Info

GTI9500 bootlooping any ROM other than South Africa 4.2.2 , invalid baseband

Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !

When you went into download mode, what was the product name the phone reported?

Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot

Screenshot is fine as it will give me what I need to know.

Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check

Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.

Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.

I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?

Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?

The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.

Deleted my OS

Help i accidentally deleted my operating system on my Samsung Galaxy S6 SM-G920F
I have tried flashing the original firmware with odin but it always seems to fail the same way and says
NAND Write
FAIL!!
i have also tried flashing roms like Cyanogen 12 and a unofficial 13 version with TWRP which is installed but this always fails as well
I would really appreciate if someone could help i am quite desperate

luka1745 said:
Help i accidentally deleted my operating system on my Samsung Galaxy S6 SM-G920F
I have tried flashing the original firmware with odin but it always seems to fail the same way and says
NAND Write
FAIL!!
i have also tried flashing roms like Cyanogen 12 and a unofficial 13 version with TWRP which is installed but this always fails as well
I would really appreciate if someone could help i am quite desperate
Click to expand...
Click to collapse
Use latest Odin (v3.11.1)
try another USB port
Check the model number again
Always flash the latest firmware.

or you can try smart switch -> emergency recovery.
Just calm down, reboot PC, start everything from fresh and do not hurry!

Samsung S5 "Invalid SIM card." error. SM-G900P

quick background. Bought a sprint S5 on ebay, floor model (SM-G900P). Android ver 6.0.1. Had it activated for Boost Mobile and was getting Invalid SIM card. Called and had new SIM sent from I think Samsung (Boost transferred me). Before I got the new SIM I rooted my phone and attempted to install Xposed Installer and framework via TWRP. I had a few problems rooting but got it to work. I could not install the Xposed framework (v 86) without my phone hanging in boot up. I uninstalled the framework via TWRP and phone is working.
I received my new sim and installed and all was good for 4 days before I got the "Invalid SIM card" again. Called boost and did the ##72786# activation reset and updated my profile. This did not fix the problem. I have another Boost S5 that we don't use so I pulled the SIM out of that one and did the reset and still have the same problem.
I did trip KNOX but don't really care about that unless it is causing a problem.
Looking for suggestions before I load stock rom with Odin and start from the beginning. Not sure that stock rom will fix the problem.

its probably a modem issue. Flashing the tar.md5 in Odin is the nuclear bomb method, but its likely going to work, if anything will.

Invalid SIM
youdoofus said:
its probably a modem issue. Flashing the tar.md5 in Odin is the nuclear bomb method, but its likely going to work, if anything will.
Click to expand...
Click to collapse
So are you saying to flash back to factory stock rom? Or is the tar.md5 just the modem ware and what exactly would I loose in flashing?
Is TWRP going to be an issue?
Thanks for any help. I am traveling for work and use my tether constantly. I can work with 3G but 4G would make my life much easier.
TIA

well, you can flash the modem by itself, but the most surefire way is to just start from scratch. Get the OK4 tar.md5 file. the twrp img and supersu. Flash the tar to get it to stock, boot it once, go back to odin mode, flash the recovery, flach supersu via twrp, boot again, get logged in to your gmail acct, do the hands free activation.
from there you can get the hotspot app or just twrp flash a rom that has it baked in. MOAR 7.0 is pretty awesome. Also, RWilco has a repository of already modded tar.md5 files for the G900P that has the hotspot already baked in. id maybe flash his OK4 tar.md5
you can try this http://rwilco12.com/downloads.php?d... Galaxy S5 (Sprint) (SM-G900P)/Stock ROMs/NE5
he has a ton of useful stuff actually! http://rwilco12.com/downloads.php?dir=
his repo and chainfires are ones that i keep handy at all times @Chainfire is one of the best devs on xda

[S6] Crashed and stuck in bootloop, please help!

Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!

MTS0 said:
Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!
Click to expand...
Click to collapse
Try this thread linked below, try the instructions in post #6. Don't use any files that are linked in the thread, they are not for your device. Make CERTAIN that you use the files for your device but try those steps and instructions, they should work the same for your device.
If the instructions in post #6 don't work, try reading further in the thread , there may be more solutions discussed.
https://forum.xda-developers.com/showthread.php?t=2302144
@MTS0, I forgot to add the link, sorry, hope it helps.
Sent from my SM-S903VL using Tapatalk

Thanks for your reply, but I can't go into recovery mode. Boot loop and download mode is the only thing it still does. I can't even turn the device off, need to wait for the battery to empty.
I was checking out that thread, they are talking about flashing the PIT and param. Do I have any chance with that? I just need to acces my data....
Thanks

Samsung Galaxy S4 "I9505" Black Edition Firmware Flash Issues

Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.

this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.