So, I tried to root my phone, following Chainfire's guide. I did everything EXACTLY as I was supposed to, but after flashing the kernel in Odin, with XWKDD_insecure.tar, the device no longer worked. It rebooted into a screen with a grey battery and the loading loop, but nothing happened. I didn't even get a chance to use SuperOneClick, because the program just stalled when it said "Waiting for device...". After about 5 minutes, I held down the power button, and then the GS2 logo appeared with a yellow exclamation sign underneath it. And SuperOneClick still didn't register the phone.
I pulled the battery out, booted into download mode again, then tried to install the factory firmware I downloaded from samfirmware.com. But then this happened:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKDJ_REV_02_CL996627.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXXKDD.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
<ID:0/004> data.img
<ID:0/004> cache.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
When I saw it, I actually felt physically ill.
So what do I do now? I have a choice of booting into download mode, or turning the phone on normally, and getting a screen that says the update fail to load. Is there something else I can do to reset factory settings, or is that the end of my brand new phone
U could still try to reflash the rom again, check if the file u downloaded is not corupted.
You have to bear in mind that Odin can be temperamental, redownload a firmware and flash it again.
Going off memory here as im not at my pc but it looks like you have too many things in to your odin program.
first thing i notice is that you have the "Re-Partition" box selected, it was my understanding you only need Auto Reboot and F.Reset Time checked.
You could also try getting the most upto date version of Odin too which is v1.85.
Also you have entered something in to the PIT section, when i flashed my device with the firmwear from samfirmware (I9100XWKDF) i didnt put anything in the PIT section.
Maybe try changing them and i hope it works.
Crucio
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Looks like you get first to brick an SGS 2 prize any way .
jje
Not a prize i would like to win heh..
Lets just hope it can be flashed again.
moparman said:
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Click to expand...
Click to collapse
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
im a rookie to
I just read the instructions to root...
Maybe it works if repartition is not checked and reflash?
I hope someone with better skills then me can help.
If i had done this i wouöd die of a broken hearth
I remember how afraid i was to flash my TyTn2 the first time..And i didnt have any problem
yeah im a rookie also, lets hope someone with a bit for knowledge can help this guy out if we havent ^^
my heart would sick too, it did a bit when i flashed the firmware and it was german that was fixed easy tho lol.
The repartition basicly changest the size of some system partitions based od the PIT file, its not recomended to use the repartition, but that shouldnt be the problem why the ODIN failed.
As he said he is able to go to download mode so he should be safe, just reflash the rom or try other rom versions and flash them.
Crucio_ said:
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
Click to expand...
Click to collapse
The screenshot I posted was from after the damage was done. I had already given up on trying to root my phone, and was trying to install the firmware from SamFirmware, in the hope that it would get my device back to factory settings.
Initially, when I flashed the kernel with Odin, nothing was selected except for "Auto reboot" and "F. Reset Time", and the only file loaded was the XWKDD_insecure.tar on the PDA line. I was also using Odin3 v1.85 at the time. The firmware I downloaded from SamFirware came with v1.83 and I didn't even notice that it wasn't the latest version.
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
rheedan said:
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
Click to expand...
Click to collapse
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
bilboa1 said:
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
Click to expand...
Click to collapse
I don't know if I should be comforted by the fact that I tried to do the right thing, or disheartened by the fact that doing the right thing didn't solve my problem.
Is there perhaps another way to go about the whole process? Should I try another ROM? The one I used was a European XWKDF Gingerbread 2.3.3, but I also have the Russian XEKDB firmware from http://forum.xda-developers.com/showthread.php?t=1057535 - I think it's 2.1.1.
there is not much experience with the SGS2 yet and I don't have one yet personally. Never saw that one error but form the SGS1 experience i'd say try reflashing, and try flashing other SGS2 firmwares ;-)
i havnt flashed mine yet but will wait till i get insurance for the phone because (and i mention this so that people can do the same thing if they wish).. if it does brick then the option of it "accidentally falling onto a busy motorway" is open to me lol
OK, looking at your screenshot, you flashed too many files, and reformated.
Follow this guide.
http://androidadvices.com/how-to-up...ii-i9100-to-gingerbread-xwkdd-2-3-3-firmware/
Make sure you download the files from there as well. I have flashed mine with them after I broke a few things playing, and it worked fine after.
This will get you up and running again.
Then for Root, go to this thread
http://forum.xda-developers.com/showthread.php?t=1056334
Download the XWKDD_insecure.tar file
Odin, Without repartion checked.
Only files to link are the pit file, in pit and XWKDD_insecure.tar in PDA
Then you can use SuperOneClick to add root.
Don't panic, I doubt its a brick.
Good luck
Broomfundel said:
Don't panic, I doubt its a brick.
Click to expand...
Click to collapse
It is fairly hard to brick a Samsung properly, without actually trying... Hope that's some reassurance.
The fact you can get into download mode is a reassurance, as that should be the key. I've not owned a Samsung device, so I won't try and advise how to fix it, but I'd agree about trying that above link to install the "beta" firmware.
ODIN is pretty good, but there isn't much experience in flashing these yet, as I don't know of any devs with them. I might go out at the weekend and get one, but I'll not be starting properly on it until June realistically...
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
dhruvmalik said:
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
Click to expand...
Click to collapse
now i will never root my s2 when i will get it, faced the same sitution with my n8 once
Related
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
Ok so last night my phone froze up while I was browsing the web (it froze just after rotating, if that's of any significance) so I held the power button down until it turned off. Trying to turn it on again, it just sat at the galaxy s 2 logo before any bootanimations etc start playing.
I thought I'd try to just re-flash the ROM (CM10 nightly 26/9/2012) and it seemed to just freeze up near the end of the flash, so I left it to do it's thing.
When I returned to the phone, it was showing me a kernel panic screen, so I held the power button to turn it off again and since then it won't boot into the ROM, it won't boot into recovery, and until just now it wouldn't be recognised by odin in download mode.
I had tried installing the USB drivers for the phone etc and it wouldn't work, however while writing this topic I just got a notification on my PC saying USB drivers had been installed and Odin seemed to recognise my phone, so I tried flashing cm9 resurrection, however it seems to be stuck. These are the messages in Odin, for reference:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
and it's just been stuck there since I pressed start. There is no progress bar or anything on the phone either. Oh, and Odin's progress bar thing at the top just says "KERNEL" with a blank bar under it and "0:[com3]" with a yellow background below that.
Is it safe to unplug the phone and try again with a different USB cable?
EDIT: After trying different methods to recover it (with the same result from Odin):
Orkane1989 said:
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Click to expand...
Click to collapse
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
So it's safe to unplug the phone?
D3_ said:
So it's safe to unplug the phone?
Click to expand...
Click to collapse
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Orkane1989 said:
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Just tried this, getting the same thing, Odin gets the first "bar" in the progress bar completed and seems to get stuck. Same output as above.
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
You will have to consult someone with some more knowledge about this than me. You could have a corrupt data partition... but its honestly out of my league now lol. Sorry I couldn't help.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
Click to expand...
Click to collapse
According to the output it gives me (in the OP) it does successfully check the MD5 though.
I'll admit, I haven't actually used Odin since I first rooted this phone (back in december last year) so I'm back to knowing basically nothing about how it works.
Yes it does confirm the md5
But after that it sends the commands to start running the new kernel (basically installing it on the device firstly)
Which is where it gets stuck.
Sent from Jelly Fuelled SGS2
Just tried this: http://forum.xda-developers.com/showthread.php?t=1457458
Same issue with flashing those files.
I don't want to try the .pit because if it doesn't flash then I'll be pretty f*cked, right?
I would try what ever else you could find because if you get that guide wrong you could end up turning your phone into a paperweight. But if you so have to use the guide take note that you ahould try flashing the files WITHOUT .pit or repartition first. If that doesn't succeed than your last option is to use the .pit file and repartition.
Sent from Jelly Fuelled SGS2
I did try it, without the .pit/repartition as the guide says to try it without it first, but again, it won't flash anything (which is why I don't think I'll try the .pit/repartition)
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Sent from Jelly Fuelled SGS2
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
Hello to all the devs in the forum and thanks in advance for the help that you will give me. Please bear with me, trust me I have made sure that seeking for help was my last resort seeing as I don't want to be just another guy with a bricked phone problem. Fortunately the forum has been quite educational and I have all you guys to thank you for that.
Now then, last night I decided to root my phone because it was running a bit slow and decided it was time to do it.
Everything went fine, I managed to root it successfully, installed Clockwork Recovery and all that, although when it said that backing up the image I think was an error, I sort of just disregarded it. I booted up my phone and everything is fine, I installed Titanium Backup Pro and deleted some of the bloatware that was in my phone.
Now this probably where my phone got on its way to being bricked.
Along with the bloatware that was deemed safe on the website, I also mindlessly uninstalled the Samsung Home and probably the stock keyboard app.
I deemed them unnecessary because I was running Go Launcher EX app as my launcher and Swiftkey as my keyboard app.
What I didn't know is that all the custom roms are probably going to be using those stock apps as base. Did I assume this correctly?
So then I tried to flash the custom rom that I found appealing, followed the steps in the guide that accompanied it, and when rebooted it, it was stuck in the Samsung logo screen.
Fortunately I planned ahead a bit, although not as much as I'd hope for, I knew that I can restore through CWM but unfortunately, the restore point that it created presented with an error and I can't restore it.
So I resorted to flashing a stock rom through ODIN and followed the steps in unbricking the phone.
I encountered some difficulties with regard to the drivers and all that but I managed to have the correct ones installed.
Now comes the final problem
As I am trying to have ODIN flash the stock rom, it wouldn't continue as it does in the videos that I watched. It would always stop in about 10 seconds and say that it failed.
I tried another stock rom from a different location and it still wouldn't work.
I have also run ODIN as an administrator, and this presented:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iDXMC1_S5830iOLBLD1_S5830iDXMC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> BcmCP.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Again it only took about 10 seconds to stop.
I am running ODIN 3 v1.85
I have also uninstalled KIES.
Whenever I would cleared all the cache and mount everything sometimes it would bring me to the android setup at startup, but if I try to type there is no keyboard that would popup. And if I choose skip it, it's just black, but if I lock it, the blue stock lockscreen appears. Nothing else after that.
I decided to post as a last resort and knowing that I have done all in my ability to repair it.
So there it is, I tried to be as specific as possible to the things that I have done throughout the day,
A couple of solutions I found as I searched was to try to flash a stock rom through CWM, another suggested to use a different version of ODIN.
If someone could please point me to the right direction as to how to repair my device, it would be hugely appreciated.
Thank you very much for your time.
UPDATE: While I'm writing this I tried the latest version of ODIN and it still won't work. Same issue. Please help
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Hitesh2626 said:
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Click to expand...
Click to collapse
Hello Hitesh! Thank you so much for your correspondence. I've been seeing your consistent replies to people who have the same problem as I had.
As for my phone, I managed to unbrick it yesterday by flashing a different custom ROM through CWM. I am currently running Extremis 2.1 from destructo570
Again thank you very much for your help.
As an advice to anyone who will have the same problem in the future, make sure that before you install a custom ROM to clear the cache and all that. Good luck!
Hi
I am in a serious trouble.
I am having a Samsung Galaxy S2 GT-I9100G
Its running on Stock Rom JB v4.1.2
I wanted to update it to Kitkat 4.4.2 by CyanogenMod 11 Custom Rom.
In order to do that i have rooted my phone using VRoot.
Installed CWM Recovery 6.0.1.2
Copied the ROM files and Gapps to SD Card.
Done all the prerequisite and started installing the ROM.
Then the installation failed showing Error Status 7.
Upon googling about status 7 i got to know that the CWM Recovery 6.0.1.2 which i used doesn't support for
installing CM11.
Then i searched for the latest CWM Recovery and got to know about the Philz CWM Touch Recovery 6.0.4.5
I also got to know that in order to install Philz CWM Touch Recovery 6.0.4.5 you need to have a PC with Odin
v3.09 installed to flash this latest CWM Recovery.
Then i downloaded philz_touch_6.19.3-i9100g.tar.md5.
Installed Odin v3.09 in my PC.
Gone into Download mode by pressing Home + Volume Down + Power Button then warning screen came up then by
pressing volume up i came into download mode.
Then i connected my device to PC using USB cable. I got the added message. I also got the COM Port number.
But instead of Yellow as said in the tutorial i got Light Blue Color which i ignored. I thought the Odin
software might had made any changes to their software.
I clicked the AP button and selected the TAR file downloaded then clicked the START button.
Again failed. I don't know why that happened.
I removed the USB cable and reinserted then done the same. Then some message came and process is going on...
waited for 20 mins till nothing was happening.
Fed up of all the process i removed the USB cable thinking of forgetting Kitkat and use the stock rom.
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Please help me in recovering my phone to Stock ROM or Custom ROM.
Last hope is jig. It force download mode when.you cant by pressing buttons. If this doesnt help i think that your phone is now a clip for paper. In odin you should choose pda and after that choose kernel. I never had blue sign in odin but i had i9100. You should from the beghinig try philz kernel to root amd get cwm recovery. So as i sad you must try jig usb very cheap thing or you can do it by yourself. Maybe you should either try kies and kies recovery firmware.
Wysłane z mojego D5503 przy użyciu Tapatalka
adithyagem said:
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Click to expand...
Click to collapse
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Newer versions of Odin have blue in the ID:COM field.
Done as said by you
Hopper8 said:
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Click to expand...
Click to collapse
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
adithyagem said:
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
Click to expand...
Click to collapse
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
The ability of people to read & comprehend the help they've been given here & then actually do what's been suggested seems to get worse & worse as time goes by.
Give some very specific advice (step by step stuff, or refer them to step by step stuff), they go do something completely different. I mean, if that's going to happen, why bother asking for help in the first place ?
@MistahBungle, read the edit on my previous post (if you haven't seen it already). Do you agree the only chance is a stock ROM? I don't know, I don't see many this stuffed up very often.
Edit: Unless, there is a Philz for i9100g. But I can't find an XDA thread for it just by having a cursory glance.
Yep. Flashing a stock rom & praying is pretty much the only option. Classic case of 'attempting to do without learning'. Imagine how much **** these people would be in if the half dozen of us or so who post most of the useful help here decided to move on ?
I did find Philz for i9100g, but it's ages old (newest one I could find was 6.19.3, think Philz is up to 6.30.something). There's also no xda thread for it, so I'm tipping that the i9100 version has been flashed. Still not holding high hopes even with a correct stock ROM.
I know, there's less people here than when I started by a long shot. You're by far the most active on here, but I thought you had an S4? I'll be getting the N5 in a month or so. I still plan to be in S2 threads but obviously to a lesser extent.
I do have an S4, but apart from the first couple of months, lost interest in modding it. I want stuff to 'just work' these days for the most part. I do run a custom rom/kernel, I just haven't changed it in ages & not interested in anything that trips Knox. Just can't be bothered putting up with stuff not working/spending a lot of time trying to make it work.
So...I accumulated a lot more knowledge of the S2, given I spent 18 mths or so actively modding it.
Understood. Yes that's what seems to be happening more now, phones which, if they're not on stock ROM, lose a lot of functionality/have stuff 'not work' for whatever reason. Like the GNote & its S-pen, HTC One and boomsound, Sony and its Bravia engine. I assume you still own the S2 anyway...
While you're here, is there anything in the Odin troubleshooting guide you've noticed which should be changed? I read over it again the other day but couldn't see anything major. If you don't want to read/comment no problem, asking as you're the resident Odin guru.
Yeah still have the S2. Haven't switched in on in 6 mths tho.
Nah, you've got everything covered in your thread. It's a great resource ('Odin expert' ? Hardly. I just read/learned a lot )
Mmm I imagine it's not the greatest experience after using a phone 3yrs newer for a while Cool. I added a couple little things just now (another pit file thread (shudder) which is quite well done & re-hosted the 3-part firmware instead of dropbox. Nothing special). Ok, call yourself what you want but what I'm sure of, is that by being on Q&A so much you have a lot more troubleshooting knowledge than probably anyone else for S2
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thanks Hopper for the help...
I have downloaded the Stock ROM for GT-I9100 Indian Version from Sammobile. I don't know what is 3-part firmware.
Now what i am going to do is Connect the phone to my PC showing (Firmware update encountered an issue. Please select recovery mode in Kies & try again) screen.
Then by clicking AP button selecting the TAR file extracted from the Zip file (Stock ROM).
Double check that only AUTO REBOOT & F.RESET TIME checkboxes are selected.
Hit Start and try my luck.
Shall i go ahead. Waiting for your nod...
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
MistahBungle said:
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
Click to expand...
Click to collapse
I have downloaded I9100G firmware only...
sorry it was my typing mistake
really sorry to panic you
I have also got a DLL file in the ZIP which i have downloaded. What is it?
Throw the .dll away, you don't need it.
Thanks to Hopper8
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thank You so much
I got my phone back to the original state:laugh:
Thank You so much for your help...
...