Alright so, Im coming back from CM7 because I was having issues with the deep sleep thing and followed kidserious's post on coming back from CM7.
Now when I tried to do it my computer reads this.
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
Its been stuck like that for over 10 minutes. Is it safe to unplug and try again or should I leave it in there?
P.S. 400TH POST!
OK took a leap of faith and unplugged it and tried again, and IT WORKED!
Now when I boot the phone right after the Odining, it boots into the stock recovery and when I click Reboot it boots me right back. What should I do?
What rom are you trying to go to now?...if your going from cm7 back to anything else your probably gonna want to odin the atlas 2.2 pit file and check the repartition box....tar file always goes in PDA button NEVER PHONE! odin and an official vzw tar file ( I suggest eb01) and let it boot fully, then you can pull the battery and odin a new recovery...after that boot directly into recovery (if you let the phone fully boot you will have to re odin recovery again) wipe data/cache/dalvik and flash new rom and kernel and you should be good...pm me if you need more help
Sent from my SCH-I500 using XDA App
After the Odin is complete I try to turn the phone on and automattically get put into stock recovery. When I click reboot system now, I get put back into the same recovery.
So I'm going to have to do this today only I'm going to dlo9 with pit....once i do this can I just receive ota updates to Edo4
Edit its my gf phone I don't think I want to mess with root stuff anymore on a Samsung to much work
Sent from my ADR6400L using XDA App
Related
hey guys, had the gs2 a few months now and decided to root it tonight.
plan back fired. stuck with the samsung logo and the ! symbol.
original info:
GT-I9100
2.3.3
I9100NEKF2
2.6.35.7-I9100XWKF4-CL280512
[email protected]#2
Gingerbread.XWKF4
Click to expand...
Click to collapse
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4
is what i tried to flash this with (odin).
Went through all the steps. flashed, blue bar came across. said success in ODIN. Phone rebooted but wont get past the ! screen.
have tried flashing with I9100XWKF4_Kernel and tried reflashing with CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4, Both result in same issue (phone stuck on boot screen with ! symbol).
Any ideas on where ive gone wrong? or possibly a way to resolve this?
Thanks again
rossonza
can you enter download or recovery mode? (volume up + home + power // volume down + home + power)
If you can go in recovery, wipe data/cache factory reset + wipe cache + advanced and wipe dalvik cache.
Mount usb storage and put in your internal memory a rom (like batista or villain rom or checkrom your choice, i use batista) flash that one and reboot.
If you can only go in download mode, try to flash the lite'ning 6.1 (KH3) rom, be sure to DONT check repartition (that will brick your phone).
The lite'ning already contains root (no need to use cf-root before) so if you can enter download mode, it's a good choice to "unlock" (hopefully it works) your phone.
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Well, the rooting process didnt worked well if you cant even enter recovery (that comes with the rooted kernel).
Keep me informed if you can fix the problem.
I forgot to tell you, you can also flash from download (maybe you prefer) a stock original rom (from this forum, S2 Android Original Development) so you get back to the stock rom (without root).
im downloading both the custom liteneing rom and the stock firmware. Ill let you know how it goes.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
<ID:0/003> Added!!
<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> Sbl.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
GT-I9100_H3G_I9100XWKF4_I9100NEKF2_I9100H3GKF1
That's not looking bright.
Im sure it can be fixed since you can enter dw mode and Odin finds / connect at the phone.
Try with the stock one, if also that one isnt working, you need a more experienced advice from a "veteran" of the forum
Stock not flashing either, both failed :S
really hope i havnt destroyed this phone. nexus one was a breeze to root.
phone gets into download mode no issues and ODIN picks it up.
rossonza said:
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Click to expand...
Click to collapse
If (never could?) means also on stock firmware then this was the first mistake.You need to try and flash your original FW (or another from XDA if your phone is unlocked) to get recovery.Without it you wont root or install ROMs.
http://www.multiupload.com/N5RWCXT1LJ
i imagine youve already got it but stick it in pda and try it.It might take a few trys but give it few goes.I had an i9000 jtaged that came back without recovery mode and it took me a few failed attempts before it finally passed and rebooted with recovery and then your away laughing.
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
If your download count (download mode) is set to 0, it is covered by your warranty.. if it's more than 0, you need a jig to set it to 0.
Kinda strange problem you got here, phone is not bricked (since odin find it and you can access dw mode) but looks like it refuse any kind of firmware.
Anyone else a suggestion? im sure big names of the forum can help out a bit here...
rossonza said:
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
Click to expand...
Click to collapse
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
rossonza said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
Click to expand...
Click to collapse
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Red_Vex said:
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Click to expand...
Click to collapse
Wrong, Lite'ning package is a ODIN package, not a clockworkmod package, i did flash the rom 3-4 times in the last 2 months with odin.
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
rossonza said:
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
Click to expand...
Click to collapse
Download mode does not mean its bricked or not bricked it just means on a bricked phone you stand a chance of recovery but that depends upon a number of factors the principle one in all this flashing is the user .
It may that multiple flashings have messed up or that the wrong firmware has been flashed .
My steps would be .
One reset rom counter with USB jig to clear for warranty.
Two Recovery mode Mounts and storage Format data cache system dalvik and sd card .
Power off boot to download mode and flash a full stock rom via Odin .
Do not use any firmware you have already used .
jje
recovery mode isnt available so cant mount.
anyone else care to input?
cooza said:
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
Click to expand...
Click to collapse
Thanks that firmware fails, Whats a JTAG?
i dont mind paying to get this fixed if thats what it comes to.
cheers
Why not try to re-install the drivers?
I got problem flashing the rom, but rectified it after re-installing the drivers.
May help u.
HI.
I had installed Odin and flashed the touch CWM 6 to my phone then I installed PureHD custom rom.
I noticed that the phone would reboot on its own every now and then.
But when it reboots, it just goes into a boot loop up to the logo , then reboots again.
Till I take out the battery, wait a little while , then re-insert the batter.
After that the phone will boot "normally" and would be functional for some time again.
I decided to change the Firmware, so i downloaded the cm-10.1-20130701-crDroid-build5-i9300.zip and install it.
That loaded fine for the most part.
I say that because when i try to use the sms application i noticed 2x since last night.
It does the same thing. It just reboots and get stuck at the logo once again.
Also I cannot copy items to my phone when its connected to my computer via the usb cable.
It tells me "cannot copy to device, either the device has either stopped responding or has been disconnected.
All this is very frustrating.
I am thinking about trying to load a stock rom via Odin to see if that will help.
Any ideas will be greatly appreciated.
Thanks..
Protorianbz
[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
Wipe phone and flash stock rom.
jje
I tried that.
I tried to isntall the STock rom.
It was installed via Odin successfully.
I saw the green Android man for a split second.
And phone just reboots, and now is stuck in the boot loop to the logo..
then reboots again..
This is the output form Odin 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_HOME.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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
have you tried a hard reset? format data , cache and dalvik in recovery? after you successfully flashed stock rom? hope that helps
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Just wipe phone and install stock rom
Sent from my GT-I9300 using xda premium
Thread moved to proper forum.
DiDA™ said:
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Click to expand...
Click to collapse
^^ What s/he said...
You don't mention the word wipe so I figure you didn't do that. If you can't get into the phone you should do your battery-removal thing and let the phone get into the OS, then connect USB and copy out the files you need to save. If you've got a backup to your extSDcard that would be helpful - you can always restore data from an advanced CWM Restore setting.
Copy the ROM you want across to the estSDcard using USB
Download megawipe, copy it to estSDcard and flash it in CWM.
Flash your ROM and restart phone, Set it up and once done, then start adding apps and restoring data, THEN make a full backup.
As a rule, the only time you do not do a full wipe of your phone is when you are flashing a point upgrade. i.e. going from AbcROM 7.1 to AbcROM 7.2 - if you are changing ROMs or doing a full step upgrade (AbcROM 7.x to AbcROM8.x) you need to do a full wipe to avoid problems.
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Dolphlungegrin said:
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Click to expand...
Click to collapse
Solved.
Fix:
Resinstalled Odin (wouldn't let me run as administrator before. Reinstalled Me7 from zip (extracted). Booted up Odin. Unchecked repartion. and voila. It re-flashed successfully.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
i had the same problem. if your just trying to get unbricked i can help. (warning i am extremely new at all this). so i did the update and ever since had been trying to get root access and flash a custom ROM. i too tried to install twrp through goo manager. i kept bricking my device by trying to boot into recovery. i found out that if do a battery pull, and hold the volume down and power button (booting into recovery) but dont let go until a warning page comes up. it should warn you about installing custom roms and give you the option of continuing by pressing the volume up button, or pressing the volume down to reboot. choose to reboot and you should be back to nromal. hopes this helps and was what you where looking for.
Dolphlungegrin said:
Solved.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
Click to expand...
Click to collapse
There is currently no way to install a different rom after taking the ME7 update. You cannot go back to MDK either.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
So, was working on flashing a custom ROM on my wife's phone (I've flashed phones countless times, even plenty with Odin), but after an issue flashing the Recovery, the phone wouldn't boot and would go straight to the Download every time. I've tried flashing a couple ROMs via Odin, but kept getting an odd message until I applied a PIT file. The phone booted back to how it was successfully.
Seems the Recovery is messed up though, so I need to try and fix that.
I tried to use Odin to apply a factory image, but it failed (see phone screenshot attached and Odin log below)
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Went to reboot back into the OS, but now it goes to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried this last night, but it said my phone was unsupported...
Ugh, finally convinced my wife to get a smart phone and now all of this...
You're trying to flash an MJ7 build. Is that the build you had when you started? I'm thinking you'll need to try the NC5 full wipe tar file with Odin.
The Verizon S4 is pretty locked down. Unless you have a phone with an MDK build, you will be extremely limited as to what you can do. Best to do a little research before you brick your phone permanently.
Sent from my NCC-1701 using Tapatalk.
I was able to get it to boot back to the prior running version after applying a .pit file (I thought that would have wiped everything)... Determined that it is FNC5 and flashed with that. It apparently didn't wipe the data, but I did a factory reset afterwards. I noticed though that now WIFI won't turn on... Really need to get this working well one way or another...
Interestingly enough, I have another of the same model phone that I haven't had any issues really with...
If I could just get a working recovery on it, I have a feeling I would be fine (I could just flash the same ROM as I have on my other phone AND make sure things are actually wiped!).
If I try to push about any recovery console via several methods, they all fail. Is it possible that the partition or something is messed up? Any sure fire way of fixing it (or a good route in the right direction)? I would LOVE to take this phone even back to 100% new phone, wiping out everything...
@riker147 MDK build? I don't see a version that had MDK in the version for my phone... SCH-I545 (Verizon)
MDK was a very early build.It was the only one that could have a custom recovery because of an exploit that was found. A later update fixed that exploit. (No, you can't revert to an earlier build) Now our only option for any type of recovery is Safestrap. Just be aware, Safestrap is very limited. Like I said earlier, best to do some research.
Sent from my NCC-1701 using Tapatalk.
I need some help with my SGS2.
I was on custom rom CM (6.0.1) with Team win recovery. I wanted to give away my phone to an elderly person and tried flashing the stock firmware with ODIN 3.
All went well but after restarting the phone is stuck at Samsung boot animation for long time.
I tried reflashing, restarting, wipe cache partition, factory reset etc but nothing worked.
Any idea how to come off this?
galaxyII said:
I need some help with my SGS2.
I was omn custom rom CM (6.0.1) with Team win recovery. I wanted to give away my phone to an elderly person and tried flashing the stock firmware with ODIN 3.
All went well but after restarting the phone is stuck at Samsung boot animation for long time.
I tried reflashing, restarting, wipe cache partition, factory reset etc but nothing worked.
Any idea how to come off this?
Click to expand...
Click to collapse
You repartitioned your phone to install cm13
So you have to repartition your phone again with stock pit or a pit that have 1.5gb system and 512mb preload to install stock rom , you will find all needed pits in the repartition thread by Saber.
Flash the pit in odin with CWM kitkat compatible recovery, reboot to recovery and wipe data, cache, dalvik cache, system, and internal storage then reflash stock rom and it should boot
MigoMujahid said:
You repartitioned your phone to install cm13
So you have to repartition your phone again with stock pit or a pit that have 1.5gb system and 512mb preload to install stock rom , you will find all needed pits in the repartition thread by Saber.
Flash the pit in odin with CWM kitkat compatible recovery, reboot to recovery and wipe data, cache, dalvik cache, system, and internal storage then reflash stock rom and it should boot
Click to expand...
Click to collapse
Thanks. I followed Saber's thread and started with PIT file. all went well.
I tried to flash the stock rom, I am stuck in ODIN at Flashing factory.img
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
Any ideas how I can proceed?
Update: it worked! i changed the ODIN version and flash was complete and I am able to use the phone.
Thank you very much @MigoMujahid
galaxyII said:
Thanks. I followed Saber's thread and started with PIT file. all went well.
I tried to flash the stock rom, I am stuck in ODIN at Flashing factory.img
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
Any ideas how I can proceed?
Click to expand...
Click to collapse
galaxyII said:
Update: it worked! i changed the ODIN version and flash was complete and I am able to use the phone.
Thank you very much @MigoMujahid
Click to expand...
Click to collapse
Good to know it worked , always use Odin 3.07 or 3.09 , i always get issues with Odin 3.10.x
MigoMujahid said:
Good to know it worked , always use Odin 3.07 or 3.09 , i always get issues with Odin 3.10.x
Click to expand...
Click to collapse
for me the
PIT file flashing worked only in Odin3 v 1.85
Flashing ROM worked only with Odin3 v3.07
Thanks once again.