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.
Related
Hello! I'm really interested in trying Litening's ROM and I've tried multiple times. I've followed the instructions EXACTLY as written. I searched around the forums and also tried running the Kernel Cleaning Script before flashing but to no avail.
No matter what I do, after Odin finishes flashing, my SGSII boots up to the dreaded Kernel Panic Upload mode....
The ROM from which I'm trying the Litening ROM flash is ICS 4.0.3 XXLPB.
Please help and thanks!
One download a new copy .
That fails try a different rom .
jje
sometime it happened to my phone also.
not with specific rom,but i happened.
If coming from ginger,did u update your bootloader,if not flash with 512 pit file and tick repartition,then flash with Odin
Right way to flash with Odin
1 open Odin
2 set the files(rom)in Odin
3 reboot phone into download mode(fully recharged battery
4 connect to odin
5 wait for for Odin to confirm your phone(03 or 07) and flash
6 phone reboots...done
Kernel panic uplod mod
This is really a PAIN giving PANIC now....
People who flashed freshly ICS rom including Bootloade have also got this PANIC,
I have never flashed an ICS rom from ODIN, flashed ICS from CWM on my GB, I have got once since I installed 2 days back....
I was thinking that, this virus was spread from leaked ICS version but no, this PANIC is there from 2010, people who upgraded from 2.3.3 to 2.3.5 also had got this...
ONLY SAMSUNG KNOWS WHY THIS IS HAPPENED
it is not caused by any KERNEL,
it is not caused by any Bootloader
it is not caused by any version of firmware
something somwhere a mismatch between firmware and hardware happens...
Only a remedy for this issue is to Keep on changing the ROM until you get the one without this issue.....
Thanks to all for your replies.
I indeed downloaded a fresh copy, also tried different versions, same result.
ZACQ8, I actually read another reply you posted somewhere else about flashing stock GB first then trying to flash the Litening ROM, haven't tried it yet, but will try it and then report back.
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'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
I have a SM-N900P, rooted stock ROM, CWM recovery, and the hotspot mod. All came from galaxynote3.com if that helps. I was wondering how I would go about updating my phone to 4.4.2. Obviously when I try to update it tells me it can't because of the root. I tried unrooting my phone by flashing the stock firmware but it failed every time, through every USB port. I tried upgrading my phone through Kies but I can't find my S/N.
lilkounchry said:
I have a SM-N900P, rooted stock ROM, CWM recovery, and the hotspot mod. All came from galaxynote3.com if that helps. I was wondering how I would go about updating my phone to 4.4.2. Obviously when I try to update it tells me it can't because of the root. I tried unrooting my phone by flashing the stock firmware but it failed every time, through every USB port. I tried upgrading my phone through Kies but I can't find my S/N.
Click to expand...
Click to collapse
Post #5 will get you all hooked up! DO NOT try to revert back to jellybean once you have flashed NAB through Odin.
http://forum.xda-developers.com/showthread.php?t=2656802
Had been running Hyperdrive rls 20 on what was a "backup" phone so I was unfortunately getting careless loading roms. At any rate, I attempted to upgrade to HD rls 21 and ran into a problem on reboot. The phone was extremely slow and I kept getting an error message "com.android.keyguard quit" or words to that effect. At this point I was still able to get into recovery (stock) and download. So I tried to flash release 21 several times without success. Out of frustration, I tried to download (odin) so-called emergency repair roms. They were 4.2 or 4.3. Subsequently I recall reading some time ago that there is a real (unrecoverable) problem that occurs if you ever try to go backwards from 4.4 to 4.3. My guess is that I am experiencing that "real problem" right now, because all I can get is "Firmware upgrade experience a problem; use Kies etc..." I tried Kies and it can not connect with the device. So not able to get into recovery and not able to get into download. Is the situation beyond hope. Please advise.
Can you get to stock recovery? You could try doing a factory reset from there at least...
ammjr71 said:
Can you get to stock recovery? You could try doing a factory reset from there at least...
Click to expand...
Click to collapse
Thanks for your response. No, I can not get into stock recovery, safestrap, or download mode. All startups go directly to the yellow warning "there is a problem with your firmware update". I think it is a goner but I just wanted to check and see if there was some trick (or miracle) I had overlooked. Looks like I have a new paperweight.
Yep, you are screwed. Never use the wrong Emergency Files.. Also, RLS 21 Needs another ZIP to function. Its the step after the actual ROM flash...