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
Related
I have the AT&T SGS2. I had installed a few custom software a few months ago, but then I installed a stock 2.3.4 for the AT&T phone. The custom binary count is 1 on the recovery screen.
To upgrade to the official ICS from AT&T, I installed the latest KIES. It successfully detects the firmware update for the device. KIES starts installing and everything goes fine until almost very end. At 91%, installation fails giving the error message something like "Unexpected error. Firmware upgrade encountered an issue. please select recovery mode in kies & try again". I tried several times and same thing happens again. I also tried downloading the stock ICS and install it via ODIN, but same thing happened. It failed at the very end.
What could be happening here? Any advice? Can it be anything to do with the custom binary count? Thanks in advance...
Not sure what might be intefering with kies or Odin. Where did you get the tar that you flashed that failed?
You might try again, with the UCLE5 Stock ICS plus Root tar from the Development forum.
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .
I finally decided to update my AT&T Galaxy Note this Sunday. I already had a root on GB, so I decided to update to a ROM with root. I chose bigfau's {ROM}{UCLF6} Official ICS Stock Odexed, Deodexed, Rooted, Zipaligned, CRT ROM for the Note. However, when I went to update via Odin, I found out that I needed CWM.
Therefore, I found a GB rom with CWM, and installed that via Odin.
Then the phone restarted. It started just as normal, and I placed the ICS ROM (see above) on the internal SD card. I then restarted to CWM (this was the first time I had started CWM on this phone). I went and installed the ICS ROM via CWM. Apparently it came out fine (according to the screen). So I went all the way up, back to the original menu.
I chose the reboot option.
It rebooted, and the Samsung logo appeared.
The logo disappeared. And reappeared with more brightness.
So far, still normal.
Then the screen went black. No buttons I pushed did anything, no matter how long they were held. Only a battery reset would let me do anything with the phone. I took out the battery and put it back in, and restarted it in download mode, then re-flashed it with GB. Nothing happened. I re-flashed GB w/ CWM. Then I went back to CWM and tried installing ICS again. Same thing happened.
I went around looking for some helpful post on AndroidAuthority and XDA. Nothing.
I've run out of ideas.
So today, I ask for help.
Any help leading to a solution is appreciated.
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
The file is zipped!
gregsarg said:
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
Click to expand...
Click to collapse
Thank you, however, the file from samfirmware.com is a zip file, which I believe I'd need CWM to install (Odin only accepts tar files, as far as I can tell). However, when I unzipped it, I found a .tar.md5 file and a dll. What should I do now?
For clarification, I can't access the internal SD without it functioning, and I don't have access to a microSD card.
Unzip the file you got. The .tar file is in there.
I already did that.
I already did that. Like I said in the previous post, it contains a .tar.md5 and a .dll. What should I do next?
(Thanks for the suggestion, anyways)
the .tar.md5 is called a tarball and has the pda file, csc file, and modem file. just put the tarball in the pda section of Odin3 and flash. Make sure Kies isn't running in the background. Reboot is checked but nothing else is.
Just getting back ...
Many thanks for jumping in ranger ....
It sounds like the OP has it now ??
Time will tell I suppose ....g
Hi
I am helping out a friend with his GT 10.1
I have previosly rooted it, and I have done this operation on many devices, though its been a while. However. Now he wants to sell it, and therefore, I am trying to unroot.
I have used Odin 1.85 as many guides suggest. I have downloaded several stock roms from samfirmware, both Open Euro and Nordic contries roms. Tried 3.1, 3.2 and 4.0, but still no luck.
I've have ticked auto reboot in Odin,
F. reset time, re-partition, and flash lock are not ticked
I choose the ROM as PDA and flash
I recall using a pit file once on a device.... do i need to extract this and select it individually, or doesnt it matter?
thanks in advance
Lars
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