I bought this phone off a guy on ebay who had accidentally flashed a stock N7100 rom on to this i605 phone. The phone still booted and everything worked but the cell radios because, you know, wrong bootloader and modem firmware.
For the life of me I can't get the modem or bootloader to flash with odin or heimdall, as they'll reliably fail at the same point every time (modem.bin or tz.img is what they fail at, whichever comes first. I've never gotten farther). So I figure partitioning must be slightly wrong then, but odin hangs on "get pit for mapping" when trying to flash the pit file.
Now with multiple firmware and stock firmware flash failures, you'd think it won't boot, right? As the act of wiping or over writing and failing would mess up anything on it, right? Well here's what I don't get: I can flash TWRP from heimdall, and then a CM zip from there (only contains boot.img) and it boots like a champ!
Long story short: Odin mode says i605, can run i605 versions of android, but I believe something is still wrong with the radios/bootloader/partitions that won't allow me to flash the proper firmware from N7100 to i605 to get the radios working. Help anyone?
Related
Hi,
I received my GSII (I9100M) a few days ago and I already screw it up.
Coming from a I9000M, we could flash nearly any rom with PIT file without any problem, I assumed the same fot my I9100M but I realized yesterday that it is not the same.
When I received my phne I tried to install UGLD3 over Kies on it. The connection keeps cutting and as such I had to try to install it over ODIN. Didn't work. It gave me a "Kernel Upload Panic Mode" and I had to install UGKG2 (gingerbread) via Odin to make the phone works again.
Yesterday, I decided to try to install UGLD3 again via ODin but I also used a PIT fil included in Sammobile Odin software. Odin failed midway installing. I tried to reinstall UGKG2 and it failed again. I panic. I try UGKG2 again with PIT. It successfully installe but upon reboot, it gave me a E:failed to mount error on all the lines. I decided to reread some guides on XDA and found one that indicated that an guy with an I9100M with the same problem was able to recover the phone by installing a I9100 stock rom. Tried it. It worked. I tried to reinstall UGKG2. Failed again. Same error. Reinstalled the I9100 stock GB rom. Now the phone is working but I have a Rom not made for my carrier. I have all that junk that I don't want. I even realized that Bell is very good with it's bloatware.
So my question: What should I do to be able to make my phone works with UGKG2 again.
1) Should I reinstall UGKG2 with PIT and RE-Partition ticked this time? (it wasn't ticked last time)
2) Should I bring it to my carrier in order to be serviced?
3) Any other suggestions?
Thanks for all your help!
urself25 said:
Hi,
I received my GSII (I9100M) a few days ago and I already screw it up.
Coming from a I9000M, we could flash nearly any rom with PIT file without any problem, I assumed the same fot my I9100M but I realized yesterday that it is not the same.
When I received my phne I tried to install UGLD3 over Kies on it. The connection keeps cutting and as such I had to try to install it over ODIN. Didn't work. It gave me a "Kernel Upload Panic Mode" and I had to install UGKG2 (gingerbread) via Odin to make the phone works again.
Yesterday, I decided to try to install UGLD3 again via ODin but I also used a PIT fil included in Sammobile Odin software. Odin failed midway installing. I tried to reinstall UGKG2 and it failed again. I panic. I try UGKG2 again with PIT. It successfully installe but upon reboot, it gave me a E:failed to mount error on all the lines. I decided to reread some guides on XDA and found one that indicated that an guy with an I9100M with the same problem was able to recover the phone by installing a I9100 stock rom. Tried it. It worked. I tried to reinstall UGKG2. Failed again. Same error. Reinstalled the I9100 stock GB rom. Now the phone is working but I have a Rom not made for my carrier. I have all that junk that I don't want. I even realized that Bell is very good with it's bloatware.
So my question: What should I do to be able to make my phone works with UGKG2 again.
1) Should I reinstall UGKG2 with PIT and RE-Partition ticked this time? (it wasn't ticked last time)
2) Should I bring it to my carrier in order to be serviced?
3) Any other suggestions?
Thanks for all your help!
Click to expand...
Click to collapse
1. re-partition is very bad I think. You shouldn't have to touch anything in ODIN other than select the file you want to be flashed.
2. I don't think they are gonna help you if you have been using ODIN, but I could be wrong.
3. You should find this: I9100MUGLD3_I9100MBMCLD3_BMC (try to dl from HERE or just Google Bell stock ICS firmware). I9100MUGLD3_I9100MBMCLD3_BMC is the stock ICS firmware for Bell. Flash the TAR file using ODIN I think under PDA and not PIT. I think that should work. There are guides all over XDA to show you this so do a search before trying and follow steps in the guide you find and READ EVERYTHING YOU CAN, the more you read the better prepared you will be if something goes wrong. Actually you can flash any firmware you want the same way and then you should flash CF-Root kernel to obtain root and CWM recovery so you can never use ODIN again and just flash everything in CWM recovery. Once you get all set you should check out the development forums and I recommend to flash a custom ROM.
This is a good thread to browse through:
SGS2 Canadian Thread (Bell/Virgin/Sasktel/Rogers) Root/Unlock/Firmware/Modems/Mods
I tried updating my Galaxy S2 yesterday via Kies from Gingerbread to Jelly Bean and have encountered a slew of problems ever since. As of now, my phone is soft-bricked, only able to get into download mode or the Phone---!---Computer screen.
This is the process that has lead to my current situation.
I first installed Kies, and found out that I couldn't even get it to detect my phone in the first place, after searching threads and trying for hours to get it to detect, it did, only to freeze at 0% on the install process. I repeated this process a couple times and waited for a very long time each time before unplugging my phone in the middle of the process, until deciding to try Odin.
I downloaded Odin 3.07 and the stock Jelly Bean firmware for my SGH-i777 from sammobile.com and did exactly the steps on guides, basically putting it into download and loading the firmware into the pda section of Odin. Unfortunately what happened was that it would get stuck on different steps, usually boot.bin or sbl.bin, but never past that. After waiting and retrying again, I searched for more remedies and tried those to no avail. This is where my phone has become soft-bricked. After trying the Jelly Bean firmware I also downloaded and tried the version I was hoping to come from, Gingerbread, with the same results.
Hearing about Heimdall being supposedly a better program, I downloaded that and have been trying to use Heimdall Frontend to flash my firmware. I downloaded the pit file to my computer, seperated the original firmware file used for Odin into seperate parts, and tried to load the factoryfs.img by itself, the boot.bin file by itself, and the boot.bin, modem.bin, factoryfs.img, and cache.img, and zImage together. Boot.bin by itself gets a "failure to connect" type error, factoryfs.img by itself gets "ERROR: Failed to send file part packet! ERROR: FACTORYFS upload failed!", and the set of 5 files gets "Failed to load config descriptor."
This is where I am at a loss because now I have no idea where to go from here, I'd really prefer not to wipe my phone. Any help would be very much appreciated. Thank you.
At this point, you are beyond where you worry about wiping.
You didn't say you can get into recovery, so that is moot anyway. But if you could get into recovery and do a wipe data/factory reset, you should.
First, try using Odin3 v1.85, which was the current version when this phone first came out. I helped another person who couldn't flash with 3.07, but was able to get the flash to complete with 1.85. And if the flash doesn't complete the first time, keep trying. I would suggest flashing the full Gingerbread firmware, I777UCKH7 from the Download Repository. Or you can get it from sammobile.com/firmware.
If that gets you nowhere, follow the steps in this post.
xfill said:
I tried updating my Galaxy S2 yesterday via Kies from Gingerbread to Jelly Bean and have encountered a slew of problems ever since. As of now, my phone is soft-bricked, only able to get into download mode or the Phone---!---Computer screen.
This is the process that has lead to my current situation.
I first installed Kies, and found out that I couldn't even get it to detect my phone in the first place, after searching threads and trying for hours to get it to detect, it did, only to freeze at 0% on the install process. I repeated this process a couple times and waited for a very long time each time before unplugging my phone in the middle of the process, until deciding to try Odin.
I downloaded Odin 3.07 and the stock Jelly Bean firmware for my SGH-i777 from sammobile.com and did exactly the steps on guides, basically putting it into download and loading the firmware into the pda section of Odin. Unfortunately what happened was that it would get stuck on different steps, usually boot.bin or sbl.bin, but never past that. After waiting and retrying again, I searched for more remedies and tried those to no avail. This is where my phone has become soft-bricked. After trying the Jelly Bean firmware I also downloaded and tried the version I was hoping to come from, Gingerbread, with the same results.
Hearing about Heimdall being supposedly a better program, I downloaded that and have been trying to use Heimdall Frontend to flash my firmware. I downloaded the pit file to my computer, seperated the original firmware file used for Odin into seperate parts, and tried to load the factoryfs.img by itself, the boot.bin file by itself, and the boot.bin, modem.bin, factoryfs.img, and cache.img, and zImage together. Boot.bin by itself gets a "failure to connect" type error, factoryfs.img by itself gets "ERROR: Failed to send file part packet! ERROR: FACTORYFS upload failed!", and the set of 5 files gets "Failed to load config descriptor."
This is where I am at a loss because now I have no idea where to go from here, I'd really prefer not to wipe my phone. Any help would be very much appreciated. Thank you.
Click to expand...
Click to collapse
The inconsistency of errors might imply that either your USB cable or USB port is faulty. Try a different port and/or cable to see if you have better luck. There is one known issue with Heimdall at the moment where it fails to flash certain partitions for certain devices. However it doesn't cause any damage to the device, the flash will just stop and those files won't be replaced. However, this is not the issue you're getting (and it shouldn't be a problem with your device).
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
If someone with this new update and root could dump some images i could make an odin tar for yall.
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
im in the same boat lol....any luck bro?
Nubsta said:
im in the same boat lol....any luck bro?
Click to expand...
Click to collapse
See this thread:
http://forum.xda-developers.com/showthread.php?t=2461203
Guess I'll start at the beginning so nothing gets left out. I was rooted on OC1, downloaded FlashFire to update to OF1 . Flashed it, the phone rebooted and got stuck on the black Samsung Custom screen. I've tried to flash tar files of OC1 and everytime I put it or any kind of tar file in the AP slot of Odin, Odin becomes unresponsive and closes. I tried to load up the SD Card with OC1 and OF1 Roms and tried to flash those to see if that would do anything. The phone always says (in recovery at the bottom of the screen)- Manual mode, applling multi-csc...applied the csc-code-vzw. Then says below that, remove failed file '/system/csc_contents'(read-only file system. At the top it says Android system recovery so I'm assuming that's custom, I know its not Safestrap so I guess its FlashFires recovery? Anyway, when I try to flash a ROM it says,E:footer is wrong E:signature varification fail. I'm at a loss as to how to get the phone back, if its possible. I was always told that if the phone powers up, its recoverable, just not sure how. Any advice would be awesome, I've been messing with this thing since early yesterday and I really need my phone back!
....It seems as though I have stock recovery. Is there a way to flash a recovery through Odin?
have you tried using ODIN with I545_Downgrade_tC1.tar from [How-To] Update to I545_OF1 - 5.0.1 and KeepRoot by muniz_ri? ODIN tends to get stuck for a bit while loading the tar, as it is reading a 2gb file. You should probably leave ODIN alone for a few minutes after loading, and if it still has problems, maybe re-download ODIN or use a different comp.
Thanks for the response. I did try that file, actually that was the first one I tried but it didn't work. Actually while I was typing this I downloaded another Odin, put the OC1 neutered tar file and did what you said, left it sitting in AP. After 5 mintues or so it worked!!! I've been messing with this phone going on 3 days now and as I'm typing the phone has rebooted and now is in the setup wizard!! Thanks for the reply!
Hello I've bricked my sgs2 it's not so hard bricked. It goes to download mode easily, but the problem is I can't find 3 file rom - probably 2.3.6 android, cause every link on the interer is down [2011, 2012]. I tried flashing it with 1 file rom through odin but it fail. I need to repartition it with full 3 file rom.
Please is there anybody who can help me? Simply provide 3 file rom for odin with pit file for Samsung Galaxy S3 i9100...
Thanks
I have an untested 3 part + pit gingerbread (multi csc) firmware.....
I also have a 3 part jellybean firmware.
I can provide links to either or both of them if needed.....that is assuming your device is the international variant.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa you didn't reply yet, but I'm guessing you still need the firmware....
Here are the links.....
Gingerbread
https://www.androidfilehost.com/?fid=24269982086991760
Jellybean
https://www.androidfilehost.com/?fid=24052804347838984
The Gingerbread zip contains a pit file, but the Jellybean one doesn't. There are posts on XDA that contain pit files, you just need to search for them.
http://i.imgur.com/rVnFwJM.jpg
Thank you I hope I will unbrick my sgs 2
You have a better chance of that if you use a pit with either of those firmwares than with just the firmware on it's own......
BUT......
You are advised to use the pit as a strictly LAST OPTION.
If flashing a pit fails, you end up with a device that CAN NOT be revived/recovered......
So...bearing that in mind, try with just the firmwares first.....The theory behind them is that they will format the partitions and erase ALL traces of previous software without rebuilding the partition layout....that is what the pit is for.....
And as I said, if the pit flash goes wrong, you end up with a device that has corrupted partitions which is then impossible to flash further.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa let us know how you get on.....
What files you flashed, what procedure you followed.....
That way, if other members face the same issue as you, they'll know what to or not to try.......
http://i.imgur.com/rVnFwJM.jpg
I tried to flash 3 files rom. Fail. I tried different computer, different cables nothing helps. Then I tried to flash kernel. Odin froze on nand writing I need to shutdown Odin after 30 minutes. I tried flashing bootloader and also Odin froze and I turned it of after 30 minutes.
I have no idea what to do....
I can turn on the phone to the download mode... Only that.
Is this possible to unbrick this phone?
Flashing with odin is a bit like the lottery....
It may not work the first 9 or 19 times, but the time after that, it does....
Perseverance is the name of the game.
Look at this thread.....
http://forum.xda-developers.com/showthread.php?t=2345831
It has been written for situations like yours.....
http://i.imgur.com/rVnFwJM.jpg