Hi,
With the semester over, I planned on tweaking my S4.
Before I began: MDK, Rooted Stock with Custom Recovery
Right now: Will boot only to Samsung Screen.
I wanted to restore everything to stock factory outta-the-box settings.
First: Flashed with Odin 3.07 the SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz on rwilco repository
Failed, Reboot shows Exclamation Point. Unfortunately I didn't record what the phone or odin said.
I then gave the ME7 firmware a shot, giving me the same result.
In a spate of annoyance, I began firing all cylinders, attempting MIJ, ME7, MJ1 stock firmwares, all giving me the same response. I tried any. (heck what they say about too little sleep... too MUCH sleep is bad for ya )
I get the following messages now when I attempt to ODIN things:
[Odin version, files flashed, Odin Response, Phone response, Restart result]
1. ODIN 3.09, with pit file and MJ7 Firmware: "System.img.ext4 fail" Start [224, 1440] Bar [240, 1440]. Restarting gives exclamation point
2. Odin 3.09, Just Pit file: "Repartition operation failed", Start [224, 1440] Secure Check Fail: Pit. Restart = Samsung Screen
3. Odin 3.07: Just pit file: Res OK (worked) = Samsung Screen
4. Odin 3.07: Pit file and COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5: "Aboot.mbn fail" start [224, 1440] Secure check fail: Pit, SW Rev Check Fail: Fused 5, Binary 3 = Exclamation Point
5. Odin 3.07, COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 only: "Aboot.mbn Fail:AUTH" Start [224, 1440] SW Rev Check Fail: Fused 5, Binary 3 = Exclamation point
6. Odin 3.07, Pit file and ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5: "System img.ext Fail" Start [224, 1440] Bar [240, 1440] = Exclamation
7. Odin 3.07: MDK Kernel only; "NAND write start, Fail (Auth) Start [224, 1440] Secure Magiccode chaco fail: Boot = Samsung screen
8. Same as 7 with the ME7 kernel.
I have also tried the .exe "one touch" file found on rwilco repository: the phone says "Secure Magiccode Check Fail: Recovery"
Am I SOL? Anything to try? Kies does not connect to the phone either. I reinstalled my windows 7 VM, and am doing it on the new one to make sure it wasn't something funky on the old one.
Try this. This is a last resort Odin file. http://forum.xda-developers.com/showthread.php?t=2507253
I had the same issues after a botched upgrade attempt from me7 to mj7.
Thanks to openyoureyes for this one.
Sent from my SCH-I545 using xda app-developers app
I cant believe you didnt ask what to do, youve now locked down your bootloader.
1. Download MJ7 pit
MJ7 pit
2. Flash this in Odin after unzipping
MJ7 full wipe
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
I cant believe you didnt ask what to do, youve now locked down your bootloader.
1. Download MJ7 pit
2. Flash this in Odin after unzipping
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Result:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone: Start[224,1440] ; BAR [240,1440]
I did this on Odin 3.09, should I be using this Odin?
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will download the MK2 full wipe now. My MD5 for the MJ7 is 406438dc1e3dd51369c25b1057874685
Surge1223 said:
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The MK2 tar file result:
Re-partition operation failed
Secure Check Fail: Pit
I tried it after putting the mj7 pit file in fresh first.
After trying this on Odin 3.09, I gave it a go on Odin 3.07. The result was slightly different: on modem.bin there was a fail, and the phone said Secure Check Fail: Pit.
The pit file is the same for both mj7 and mk2
Sent from my SCH-I545 using XDA Premium 4 mobile app
I gave the MK2 a shot- no dice. Gives me
START 224,1440; BAR 240,1440
and
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed
Is my goose cooked?
No reboot recovery and wipe cache. Then download heimdall
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
No reboot recovery and wipe cache. Then download heimdall
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it. Now, according to the README, Heimdall wants a .gz'ed file- should I zip up your MK2 file and use that?
oocytecryo said:
Got it. Now, according to the README, Heimdall wants a .gz'ed file- should I zip up your MK2 file and use that?
Click to expand...
Click to collapse
Confirm the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 is valid then delete the ".md5" from the end of the tar.md5 and gzip it (you can use 7zip or winrar)
I don't remember if you have to manually create a firmware.xml file and add partitions one by one on Windows or not but if you get an error then manually create a package to flash using heimdalls built in tools.
Sent from my SCH-I545 using XDA Premium 4 mobile app
oocytecryo said:
Hi,
With the semester over, I planned on tweaking my S4.
Before I began: MDK, Rooted Stock with Custom Recovery
Right now: Will boot only to Samsung Screen.
I wanted to restore everything to stock factory outta-the-box settings.
First: Flashed with Odin 3.07 the SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz on rwilco repository
Failed, Reboot shows Exclamation Point. Unfortunately I didn't record what the phone or odin said.
I then gave the ME7 firmware a shot, giving me the same result.
In a spate of annoyance, I began firing all cylinders, attempting MIJ, ME7, MJ1 stock firmwares, all giving me the same response. I tried any. (heck what they say about too little sleep... too MUCH sleep is bad for ya )
I get the following messages now when I attempt to ODIN things:
[Odin version, files flashed, Odin Response, Phone response, Restart result]
1. ODIN 3.09, with pit file and MJ7 Firmware: "System.img.ext4 fail" Start [224, 1440] Bar [240, 1440]. Restarting gives exclamation point
2. Odin 3.09, Just Pit file: "Repartition operation failed", Start [224, 1440] Secure Check Fail: Pit. Restart = Samsung Screen
3. Odin 3.07: Just pit file: Res OK (worked) = Samsung Screen
4. Odin 3.07: Pit file and COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5: "Aboot.mbn fail" start [224, 1440] Secure check fail: Pit, SW Rev Check Fail: Fused 5, Binary 3 = Exclamation Point
5. Odin 3.07, COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 only: "Aboot.mbn Fail:AUTH" Start [224, 1440] SW Rev Check Fail: Fused 5, Binary 3 = Exclamation point
6. Odin 3.07, Pit file and ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5: "System img.ext Fail" Start [224, 1440] Bar [240, 1440] = Exclamation
7. Odin 3.07: MDK Kernel only; "NAND write start, Fail (Auth) Start [224, 1440] Secure Magiccode chaco fail: Boot = Samsung screen
8. Same as 7 with the ME7 kernel.
I have also tried the .exe "one touch" file found on rwilco repository: the phone says "Secure Magiccode Check Fail: Recovery"
Am I SOL? Anything to try? Kies does not connect to the phone either. I reinstalled my windows 7 VM, and am doing it on the new one to make sure it wasn't something funky on the old one.
Click to expand...
Click to collapse
you are toast in going back to mdk.....and the only way to load any rom will be thru safestrap....once you moved from mdk, your bootloader became lockdown
a little reading goes a long way as this has been discuss so many times my head is spinning
Surge1223 said:
Confirm the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 is valid then delete the ".md5" from the end of the tar.md5 and gzip it (you can use 7zip or winrar)
I don't remember if you have to manually create a firmware.xml file and add partitions one by one on Windows or not but if you get an error then manually create a package to flash using heimdalls built in tools.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this is downright hilarious if anything- I made the gz of the MK2 tar, and Heimdall didn't like that, so I went to the flash section and stuck all the packages into it, the pit where it belongs, and voila!
Everything is going smoothly until it gets to 100% of "Uploading System". Then, On the screen, I see the progress bar moving beyond it's proper area, and appearing on the opposite side (pac-man style). The text on the phone now says "Invalid percent of drawing download progress bar!" and says it every minute or so, so I have it now bleeding down onto my android download icon!
Any thoughts? I've let the heimdall sit like this (if doesn't seem to have crashed) on system, because I don't want to completely destroy anything.
Damn did you by chance install safestrap ever? Sit tight I'm making you a file to flash
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Damn did you by chance install safestrap ever? Sit tight I'm making you a file to flash
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I never did.
Slowbalt said:
Try this. This is a last resort Odin file. http://forum.xda-developers.com/showthread.php?t=2507253
I had the same issues after a botched upgrade attempt from me7 to mj7.
Thanks to openyoureyes for this one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
:laugh: Worked magical for me ! Thanks
oocytecryo said:
No, I never did.
Click to expand...
Click to collapse
Ok download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
Its not the same odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a pit file. Put them in the appropriate areas in Odin 3.09 and if it goes through and trys to reboot don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
BP
BP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
AP
AP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
CP
CP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
CSC
CSC_VZW_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
PIT
MSM8690.pit
Click to expand...
Click to collapse
Surge1223 said:
Ok download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
Its not the same odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a pit file. Put them in the appropriate areas in Odin 3.09 and if it goes through and trys to reboot don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
Merry Christmas! Do you have the md5s for the individual files? The MD5 for the zip file checks out, but Odin says each of the files inside has an invalid binary. Am I missing something silly?
Edit: I removed the .md5 so that each were tar files, and tired that with Odin. Odin crashes and windows gives me the following information: Problem Event Name: APPCRASH
Application Name: Odin3 v3.09.exe
Application Version: 2013.5.24.1
Application Timestamp: 519f55ae
Fault Module Name: Odin3 v3.09.exe
Fault Module Version: 2013.5.24.1
Fault Module Timestamp: 519f55ae
Exception Code: 40000015
Exception Offset: 00133964
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 308b
Additional Information 2: 308ba88846fcea477c0aef5947bf596c
Additional Information 3: 3b65
Additional Information 4: 3b65ba98d7fdf612af8e0a1ef1df3acc
Click to expand...
Click to collapse
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon mdk packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Used the no wipe as well as an emergency root with wipe. So needless to say my system was wiped and re partitioned. The whole 9.
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good, bur my phone is functional.
I do I have an old backup when root was woeking 9erfectly n the correct pit file. Anyway to use that to flash in Odin?
Sent from my SCH-I545 using Tapatalk
Related
I have searched a lot of threads and post about bricks before posting here. It would appear that my problem is a unique combination of a lot issues.
Detailed Explanation :
I am using a Samsung Galaxy S II (GT-I9001) with the Omega Custom ROM
[ROM][XXLPH][05Mar]◄Omega ICS v3.2►.
http://forum.xda-developers.com/showthread.php?t=1489197
It was working perfectly fine for a week.
Then suddenly is stopped responding and on reboot , it just showed the Samsung start screen with the yellow triangle and exclamation.
I entered Recovery Mode and tried to restore a backup but it failed. I also tried to install the same ROM again (install from SD card) with CWM from recovery but it stopped halfway and failed to respond for over 2 hours.
With no choice but to pull the battery I did so but now Recovery Mode has stopped working. Just get the same loading screen with Samsung and yellow triangle.
However I was not worried because DOWNLOAD mode was still working. I tried flashing a stock firmware using ODIN but it stopped responding. I waited for an hour and pulled the plug.
Download mode is still working so I tried different stock rom with both single file versions (PDA) and the 3 file versions (PDA,PHONE and CSC) with pit and repartition but all stop responding after a while.
It stops at cache.img for the single file ROMs and for the 3 file roms with pit it stops responding at SET PIT File. DO NOT TURN OFF TARGET. I also tried Lightening Rom and that stopped at factory.fs NAND Write.
I checked and double checked all drivers, chaged USB ports and tried reflashing a number of times.
Now when I try to boot or enter recovery I get the message "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
Kies is able to recognize the device but it tries to connect and then says "The device has stopped responding. Reboot to fix this issue" So I am unable to recover firmware using Kies.
TLDR :
There are no driver issues or interference between Kies and Odin. The device is easily recognized and download mode is working. Just unable to flash back to stock rom using odin, unable to boot or enter recovery mode.
Right now the only consolation is that download mode is still working but I am unable to flash anything. Also I had to get stock roms form external sites and smafirmware.com because the Official Firmware Links are from multiupload and they do not work.
Are there any mirrors for the official stock ROMS?
I am trying to flash different roms with ODIN and hoping for something to happen.
Suggestions/Solution to this unique problem will be much appreciated.
This is an unusual problem.
Try to flash the Kernel only via Odin.
Do let me know if you succeed.
[email protected]!n said:
This is an unusual problem.
Try to flash the Kernel only via Odin.
Do let me know if you succeed.
Click to expand...
Click to collapse
I am now using only ODIN. When you say Kernel I assume just the small stock Kernel File (5-10 MB) and not the entire ROM (~350 MB)
In download mode, in the top left corner, the current Binary was show as "Custom"
I used ODIN to flash Stock Kernel (Kernel_I9100XWKF3) and this was the progress:
Firmware Update Start..
zImage
NAND Write Start..
Now it stops responding (waited 20 mins ) but now the Current Binary is shown as "SAMSUNG OFFICIAL"
However, I am still unable to flash a complete stock ROM and cannot boot or enter recovery.
Stock firmwares are available at samfirmware.com. Try one from there. Once you flash, do a full wipe/factory reset. Seems you'll always have to do this when going from ICS to Gingerbread.
Also, from your post above, it sounds like you are still on an ICS ROM (XXLPH), and tried flashing a Gingerbread kernel (XWKF3). This will never work...
Sent from my GT-I9100 using XDA
ctomgee said:
Stock firmwares are available at samfirmware.com. Try one from there. Once you flash, do a full wipe/factory reset. Seems you'll always have to do this when going from ICS to Gingerbread.
Also, from your post above, it sounds like you are still on an ICS ROM (XXLPH), and tried flashing a Gingerbread kernel (XWKF3). This will never work...
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
I tried firmwares from samfirmware.com. The problem is that I am unable to complete the flash process as odin always gets stuck at some point (Mostly KERNEL Stage) .
<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> boot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> Sbl.bin
<ID:0/010> param.lfs
<ID:0/010> zImage
It stops here.Unless I complete a flash I cannot full wipe/factory reset.
Also, I tried flashing an older XWKE8 Rom from samfirmware and the message "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again" has disappeared. Now when I try to boot or enter recovery there is just a mobile icon and a PC icon connected my an exclamation mark inside an orange triangle
Like you said, it may be because I was on an ICS ROM and then tried to switch to Gingerbread. If So, What ROM do I try to flash now?
Have a search for the GB bootloader and try flashing just that first .
GT-I9100_OLD_BOOTLOADER is the name of the file .
jje
JJEgan said:
Have a search for the GB bootloader and try flashing just that first .
GT-I9100_OLD_BOOTLOADER is the name of the file .
jje
Click to expand...
Click to collapse
Ok I got the bootloader and flashed it using ODIN. This is the first file that ODIN was finally successful in flashing. Thanks.
Something has changed. There is no longer a semi brick screen with the icons previously mentioned.The device now displays the boot screen showing "Samsung Galaxy S II GT-i9100" There is NO YELLOW TRIANGLE now. Finally some Progress. But it is stuck on this screen. Still no Recovery mode or normal boot.
This has however given me some hope. What do I do next?
Try a custom kernel i.e.
http://dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
lordtoeknee said:
Ok I got the bootloader and flashed it using ODIN. This is the first file that ODIN was finally successful in flashing. Thanks.
Something has changed. There is no longer a semi brick screen with the icons previously mentioned.The device now displays the boot screen showing "Samsung Galaxy S II GT-i9100" There is NO YELLOW TRIANGLE now. Finally some Progress. But it is stuck on this screen. Still no Recovery mode or normal boot.
This has however given me some hope. What do I do next?
Click to expand...
Click to collapse
If you have download mode just flash a stock rom if no download mode grab a USB recovery jig from ebay etc .
jje
[email protected]!n said:
Try a custom kernel i.e.
//dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
Click to expand...
Click to collapse
Tried flashing this. It get stuck at this stage :
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
Actually all kernels I have tried so far are getting stuck at this stage.
[email protected]!n said:
Try a custom kernel i.e.
http://dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
Click to expand...
Click to collapse
Dude. It still looks like he hasn't flashed a gingerbread firmware successfully yet. Which means he's really still on ICS. Siyah doesn't support ICS yet.
And typically, flashing only a kernel when in a situation as he describes won't get you out of that situation. Unless the reason you got into that situation in the first place was by flashing a kernel that wasn't meant for you.
Sent from my GT-I9100 using XDA
JJEgan said:
If you have download mode just flash a stock rom if no download mode grab a USB recovery jig from ebay etc .
jje
Click to expand...
Click to collapse
There was never any problem in getting into download mode. The actual problem is that ODIN gets stuck at some stage when I try to flash anything. I am unable to complete the flash.
The only success was the old bootloader which you suggested. Other than that all other kernels/roms get stuck at some point.
Most other posts/threads say that I will be fine as long as download mode is working. It is, but I am still unable to flash anything as ODIN keeps getting stuck.
Thoughts .
A guess is that something broke using PIT and repartition .
Rom download faulty no you have tried to many .
Bootloader flashes yes so Odin works .
Kies is not running in the task bar is it .
You are using mainboard USB port and Samsung cable .
If it was my phone it would be a service centre job but i would probably try just flashing a CWM and root kernel first to try and get recovery mode to format the system data and cache .
jje
Other possibilities for a stuck flash:
1. Bad cable
2. Cable plugged into a USB hub instead of directly into USB port on PC
3. Cable plugged into a USB passthrough (like keyboard) instead of directly into USB port on PC
EDIT: whoops, JJEgan mentioned bad cable and direct USB connection in his post above.
Thanks for your comments.
I am using the Original Samsung Cable and quite sure it has no problems. Also it is directly connected to my Laptop. And I have made sure there is no interference between Kies and Odin.
Maybe something broke in PIT and repartition, but i can still enter download mode. So I should be able to flash something right?
Not looking forward to taking it to the service center as I have will need to reset my flash counter. I may have to do that as a last resort but i'm hoping something will successfully flash. Like I said, I am hanging onto the fact that Download mode still works.
lordtoeknee said:
Thanks for your comments.
I am using the Original Samsung Cable and quite sure it has no problems. Also it is directly connected to my Laptop. And I have made sure there is no interference between Kies and Odin.
Maybe something broke in PIT and repartition, but i can still enter download mode. So I should be able to flash something right?
Not looking forward to taking it to the service center as I have will need to reset my flash counter. I may have to do that as a last resort but i'm hoping something will successfully flash. Like I said, I am hanging onto the fact that Download mode still works.
Click to expand...
Click to collapse
Hold up. Two things:
1. I just re-read your first post, and you mentioned GT-I9001, which is the Galaxy S plus... which is not the same as the GT-I9100, which is the Galaxy SII international edition. Is this a typo?
2. Have you been putting the .PIT file each time you flash? If so, what .PIT file are you putting, and where did you get it? Could be you flashed using an incorrect .PIT file, and need the right one.
Edit to add: you really don't have to put the .PIT file when you flash unless you ABSOLUTELY have to. I've flashed several times and not once used a .PIT file.
ctomgee said:
Hold up. Two things:
1. I just re-read your first post, and you mentioned GT-I9001, which is the Galaxy S plus... which is not the same as the GT-I9100, which is the Galaxy SII international edition. Is this a typo?
2. Have you been putting the .PIT file each time you flash? If so, what .PIT file are you putting, and where did you get it? Could be you flashed using an incorrect .PIT file, and need the right one.
Edit to add: you really don't have to put the .PIT file when you flash unless you ABSOLUTELY have to. I've flashed several times and not once used a .PIT file.
Click to expand...
Click to collapse
Sorry this was a typo. It is the GT-I9100 - Galaxy S II international edition.
I used the .PIT file and checked repartition whenever it was available with Stock Kernel. ie it came along with the PDA,PHONE and CSC files.
I also tried without the PIT file (No repartition). I did not use any incorrect file.
However, I was unable to do any successful flash. ODIN would stop responding before the PIT flash was completed. if there was no .PIT files it would stop at NAND write at cache.img or zImage
lordtoeknee said:
Sorry this was a typo. It is the GT-I9100 - Galaxy S II international edition.
I used the .PIT file and checked repartition whenever it was available with Stock Kernel. ie it came along with the PDA,PHONE and CSC files.
I also tried without the PIT file (No repartition). I did not use any incorrect file.
However, I was unable to do any successful flash. ODIN would stop responding before the PIT flash was completed. if there was no .PIT files it would stop at NAND write at cache.img or zImage
Click to expand...
Click to collapse
Ok... you said you're using original Samsung USB and you're quite sure it has no problems... but have you tried a different cable? It doesn't have to necessarily be the original Samsung cable. I use a generic micro USB cable for my flashes, and it works fine. Could be the cable went bad... or try a different USB port on your laptop. Maybe the port went bad.
Yes tried another cable as well as different ports. This should not be any problem as i am able to successfully flash bootloaders. Any other type of file, ODIN pauses at some stage and does not respond.
lordtoeknee said:
Yes tried another cable as well as different ports. This should not be any problem as i am able to successfully flash bootloaders. Any other type of file, ODIN pauses at some stage and does not respond.
Click to expand...
Click to collapse
Hmm... could possibly be a corrupted download... try redownloading the files you are flashing?
DO NOT FLASH IF YOUR ON MDK AND WISH TO RETAIN YOUR CUSTOM RECOVERY! THIS WILL REMOVE THE LOKI EXPLOIT!
This is a new update for SCH-1545 taking users to VRUEMK2. This is the stock factory image. Also, If you need to go back to stock for whatever reason and this Odin tar doesn't work I suggest using the VRUEMJ7 factory image instead. VRUAMDK, VRUAME7, and VRUEMJ7 stock Odin tars contained 14 partitions over which they would write over, VRUDMI1 wrote over 13 partitions, VRUEMJ7 also contained a pit file. However I've included both the full-wipe and no-wipe Odin tar.md5's for VRUEMK2 and in the no-wipe VRUEMK2, only 12 partitions are wrote over because it doesn’t contain persdata.img.ext4 or sbl1.mbn. The full-wipe (KIES factory image) VRUEMK2 Odin tar contains 14 partitions and its own PIT file as well and will completely wipe your device and re-partition it to factory stock
For the sake of simplicity, I've also included a mirror to the MJ7 "emergency" Full-wipe Odin tar as well. Download it here
Also incase you have MDK here's a link to the full-wipe Odin tar Download it here
@Tomsgt made a great video of the process that can be viewed here
Information:
1. ROOT METHOD here
2. Download Odin 3.09 here (Note: Bootloader = BL , PDA = AP , Phone = CP)
Download: No-Wipe SCH-I545_VZW_1_20131212083410_49ap8w990g.zip
Download: Mirror
MD5: 7C2213EC9542D61B9A6CB164DC0CDB7B
Download: Full-Wipe SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Download: Mirror
MD5: c1b8a30d6071f591cc43e85dfc2dd91b
Directions:
No-Wipe
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Click start and wait for it to say Pass!
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
Edit:
12/21/13: Included both full-wipe factory image and no-wipe VRUEMK2 Odin tar.md5's
The DL is incredible slow for some reason. Rate of like 50kbps. Everything else on my connection is fine
Topsnake said:
The DL is incredible slow for some reason. Rate of like 50kbps. Everything else on my connection is fine
Click to expand...
Click to collapse
Thanks that reminded me I totally forgot to link the full-wipe main download link lol
Sent from my SCH-I545 using XDA Premium 4 mobile app
Helping reduce the amount of questions asking where the MK2 odin tar thread is.
tl;dr Bumping the thread
Tip: the first result from Googling "vruemk2 odin tar" just so happens to be the correct one.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I just sold my Note 3 and went back to an S4. Thanks for posting. Now, I can root and get back to normal haha : )
Sent from my SCH-I545 using XDA Premium 4 mobile app
What are the dangers of using the no-wipe file? I'm doing this for my gf's phone so I'm not used to the S4, sorry. The phone is currently on ME7, I had previously rooted it and de-bloated the stock rom. I've already unrooted in preparation for updating to MK2. If I can preserve her files in the process that would be great but I'm not sure if my having de-bloated some of the unnecessary system apps will cause any problems. Thanks.
FastEddie422 said:
What are the dangers of using the no-wipe file? I'm doing this for my gf's phone so I'm not used to the S4, sorry. The phone is currently on ME7, I had previously rooted it and de-bloated the stock rom. I've already unrooted in preparation for updating to MK2. If I can preserve her files in the process that would be great but I'm not sure if my having de-bloated some of the unnecessary system apps will cause any problems. Thanks.
Click to expand...
Click to collapse
No-wipe reinstalls the contents of the stock ROM, but does not delete your persistent data or applications. Anything that you deleted from the stock ROM is restored and anything you "froze" is defrosted. In most cases, that's enough to let the OTAs complete.
Dangers? If you unplug during rooting, lose power, or something else happens, the flash can fail. Those circumstances are usually recoverable because it's damn near impossible to overwrite the bootloader so there's always something there to help you recover from an oops.
Worked awesome, thank you
I was directed here from this post http://forum.xda-developers.com/showthread.php?t=2578569&page=2
I did everything for the no-wipe but I got a FAIL. What could I have done wrong?
Thanks,
Derek
dbinnc said:
I was directed here from this post http://forum.xda-developers.com/showthread.php?t=2578569&page=2
I did everything for the no-wipe but I got a FAIL. What could I have done wrong?
Thanks,
Derek
Click to expand...
Click to collapse
Where does it fail at? Download Odin 3.07 then try again also make sure the md5 is right. Otherwise try the full wipe or MJ7 no wipe/full wipe
Sent from my SCH-I545 using XDA Premium 4 mobile app
[/COLOR said:
[/FONT][/SIZE][/SIZE]
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
5. If all else fails read below...
Alternate Emeregency Repair READ:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
If the full wipe fails, but generally this download wont be needed unless your partitions are messed up. The full wipe above should be all thats needed for most if not then download this odin tar Its not the same Odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a PIT file. Put them in the appropriate areas in Odin 3.09 and if it goes through and tries to reboot, don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
This will work better if done with Heimdall. Google how to use Heimdall because I use Heimdall on Linux and don't know how Heimdall works on Windows.
BP AP CP CSC CSC_PIT
Click to expand...
Click to collapse
This will not work for me. :/ The PIT file uploads to Odin fine but when I try to bring in any of the other files, it gives me an "invalid binary" on each one. Bad download?
nickknaack said:
This will not work for me. :/ The PIT file uploads to Odin fine but when I try to bring in any of the other files, it gives me an "invalid binary" on each one. Bad download?
Click to expand...
Click to collapse
I'm probably going to delete the alternative emergency repair directions because it requires you to use Heimdall and to extract the files one by one. The normal full wipe didn't work?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
I'm probably going to delete the alternative emergency repair directions because it requires you to use Heimdall and to extract the files one by one. The normal full wipe didn't work?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, tried the full wipe and it worked great! Thanks!
This worked to get me to mk2 from me7 without a hitch. Thank you muchly.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Edit: Fixed. Just kept trying. Tried all the way back to ME7. Did MK2 before a bunch of times, maybe 5. Finally, on that last try, it made it past system. Woot!
---------
I could use some assistance. My friend's VZW S4 was rooted on MI7. I had done that for him. He wanted to update, so I downloaded the MK2 no-wipe odin file from this thread. I checked the MD5 on the zip (it was good), extracted the tar file, and attempted to flash. At first, Odin kept telling me the phone was being disconnected/reconnected. The cable was good, but it failed regardless. On further attempts to flash the tar, it would get to the end of the system img and fail. I was trying to go from MI7 to MK2, should it shouldn't be incompatible. The MD5 was good. I tried to re-odin MI7, but it's failing with " [auth] ". I'll try going all the way back to ME7 and OTA'ing up to MK2 THEN re-rooting, but in the mean time: how could I have avoided this?
So I have the full wipe ODIN downloaded and I'm using v3.09.. Do I still need to extract the .pit file if I downloaded it seperately or can I just load the .pit file and the .tar file and be fine to start the process?
EDIT: I answered that myself. Process went flawless and my phone went from unusable to working again.
Nice!
Worked great Surge! Thank you for all that you do for this device, it is appreciated!
Do I put my phone into recovery or download mode to odin the fullwipe?
Edit: Nevermind, looks like download mode, thanks for the post! Fixed my phone
No-Wipe
Hi Surge1223
I had a problem with my S4 MK2 SS so I needed to do the No-Wipe Odin.
now everything went fine but when the OS started it keeps restarting and it stops at the Verizon animation screen.
What do you think is the problem?
Thank you.
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
Mine did this exact same thing. I later found out that you have to run Odin again and only use a pit file. Basically bring up Odin, put your phone into Odin mode, connect it, on the right hand side of the Odin screen instead of clicking PDA, click PIT. Then point to your file and click start. The file name is sch-I605-16gb.pit. Only thing is that I am unsure where I downloaded it from. There is a video on youtube on that describes exactly how to do this and I think the links to the files are on that video.
StricIX said:
Mine did this exact same thing. I later found out that you have to run Odin again and only use a pit file. Basically bring up Odin, put your phone into Odin mode, connect it, on the right hand side of the Odin screen instead of clicking PDA, click PIT. Then point to your file and click start. The file name is sch-I605-16gb.pit. Only thing is that I am unsure where I downloaded it from. There is a video on youtube on that describes exactly how to do this and I think the links to the files are on that video.
Click to expand...
Click to collapse
the pit file failed, too.
Verizons SUA ended up working with restoring device.
I got the same issue. my phone was rooted with TWRP 2.6.3.2 and flashed to customized MJ9 in this thread, http://forum.xda-developers.com/showthread.php?t=2578458&page=14
Later I would like to restore to factory default, so downloaded this firmware http://terafile.co/2146204d7383 and flashed using odin. the flash was successful, however, after it finished, it started to have the exact problem as you described.
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
---------- Post added at 03:03 AM ---------- Previous post was at 02:26 AM ----------
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
I just did Section 1B according to this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
Worked like a charm
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
nxneko said:
the pit file failed, too.
Verizons SUA ended up working with restoring device.
Click to expand...
Click to collapse
Did you take 4.4.2 OTA?
Well have you tried rebooting into stock recovery(UP BUTTON, HOME BUTTON, POWER) and doing a factory reset..then reboot?
You should always flash a image or tar in Odin WITH the pit file..bc if no pit the image could end up anywhere(rare)..
So this is what I would do..
pull battery
un plug phone
reboot into Download Mode
plug phone into different USB port
ODIN see it?
If so good!
Try to reflash WITH pit file
1. Take the NG6 OTA update (should the ota update fail see troubleshooting section below).
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key).
4. Flash the I545_NC5_Stock_Kernel.tar.md5 using Odin's PDA slot(AP in Odin v3.09+).
5. Root using Towelroot-v3.apk.
6. Power off then boot into "Download Mode" again.
7. Flash the I545_NG6_Stock_Kernel.tar.md5 also in Odin's PDA slot(AP in Odin v3.09+).
8. Download SuperSU to manage root access. Done!
Troubleshooting:
Should the NG6 ota update fail consider updating to NG6 by flashing the I545VRUFNG6 4.4.2 Full-Wipe Odin .tar then continuing from Step 2 above.
Notes & Credits:
1. After flashing the NC5 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG6 kernel your phone will once again run like a champ!
2. Following the above process will not affect User Data or your Knox Warranty Flag.
3. Due to a known bug in the official NG6 OTA you may experience random re-boots after updating. Please see @Emoraax 's thread for the solution: http://forum.xda-developers.com/galaxy-s4/general/fix-reboot-crash-problem-ng6-root-t2921584.
4. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
5. Big thanks to @Surge1223 for giving me the idea of the kernel swap way back in the day. You will notice the date of the following post is way before NC5(KitKat) was even released for the I545: http://forum.xda-developers.com/showpost.php?p=51053044&postcount=77
KeepRoot Method
Original NG6 KeepRoot Method Post (Just putting this up here if anyone is interested. This method was developed back in the day at the suggestion of a very capable kernel dev).
Alternative Custom ROM Method:
1. Backup your User Data using Safestrap's Backup function.
2. Place the I545VRUFNG6_100%_Stock_Rooted_ROM.zip onto your ext-sdcard.
3. Reboot into Safestrap recovery then perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
4. Flash the I545VRUFNG6_100%_Stock_Rooted_ROM.zip using "Stock Slot."
5. Once complete press "Home" then reboot into "Download Mode."
6. Flash the I545_NG6_Stock_Kernel.tar.md5 in Odin's PDA slot (AP in Odin v3.09+).
7. Reboot into Safestrap recovery and use the Restore Function to restore User Data. Done!
8. **Optional** Reboot into Safestrap recovery and flash the I545_De-Knox_NG6.zip to remove applicable Knox files which cause the random re-boots(Do Not Wipe Prior to Flashing!)
Notes & Credits:
1. The I545VRUFNG6_100%_Stock_Rooted_ROM.zip process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery to NG6 but does not include the NG6 Bootloader.
2. Big Thanks to @rebel1699! and the following guys for developing the above method. You will notice the date of their post is way before NC5(KitKat) was even released for the I545: http://forum.xda-developers.com/showthread.php?p=51067706#post51067706
reserved
muniz_ri said:
1. Take the NG6 OTA update.
2. **Important**Download and install Towelroot-v3.apk(internet access not required).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key).
4. Flash the I545_NC5_Stock_Kernel.tar.md5 using Odin's PDA slot(AP in Odin v3.09+).
5. Root using Towelroot-v3.apk.
6. Power off then boot into "Download Mode" again.
7. Flash the I545_NG6_Stock_Kernel.tar.md5 also in Odin's PDA slot(AP in Odin v3.09+). Done!
Notes:
1. After flashing the NC5 kernel your phone may run a little wonky, e.g. extreme lag, no wifi, etc., and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG6 kernel your phone will once again run like a champ!
2. Following the above process will not affect User Data.
Important!: Only use the files contained in this guide and follow all of the above steps in the order provided. Do not skip any steps, or you may encounter issues with your device.
Click to expand...
Click to collapse
Works! Thanks again, man. :victory:
Confirmed working.
Method works fine.
AWESOME!!!! Thank you. Worked perfectly.:good::good::good:
For whatever reason my Settings crashes everytime I check for an update. Does anybody have the ota file (or a method for doing this without the ota)?
Had to fight thru some boot looping after flashing the NC5 kernel, finally got to Towelroot between boots and activated. Flashed the NG6 kernel and all seems to be good! Downloaded and installed SuperSU and installed TB and it works! Time to do a little debloating! Many thanks!!!
rbf2000 said:
For whatever reason my Settings crashes everytime I check for an update. Does anybody have the ota file (or a method for doing this without the ota)?
Click to expand...
Click to collapse
I need it too, please.
newkydawg said:
I need it too, please.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95747613655046167
How do you do this if your on nc5 and currently rooted by towelroot? Please post the process new at this. Thanks
I am currently rooted on stock NC5. However when I download and try to install the update, it goes through the install and then it just says Error! and when it reboots it says that it failed to install but no indication as to why. Am I missing something? Is there something I should be checking?
TheCrowing said:
I am currently rooted on stock NC5. However when I download and try to install the update, it goes through the install and then it just says Error! and when it reboots it says that it failed to install but no indication as to why. Am I missing something? Is there something I should be checking?
Click to expand...
Click to collapse
When taking an OTA, everything has to be original. Meaning if you root and uninstall a system app, say Verizon Navigator for example, you have to reinstall that app and anything else you modified for the OTA to work. The quickest, and easiest way to make sure everything is reset is to flash in Odin the no-wipe NC5 file (find everything you need here http://forum.xda-developers.com/showthread.php?t=2735172 )
Then take the OTA and follow this threads instructions on root.
IMO though, I wouldn't even take this update, its so minor and we are on the verge of Kexec support. We even have a safestrap that allows slots thanks to muniz...
Thank you for the quick reply! I used to have MDK until I bricked it so official updates are new to me. I might hold off then. Thanks again!
TheCrowing said:
I am currently rooted on stock NC5. However when I download and try to install the update, it goes through the install and then it just says Error! and when it reboots it says that it failed to install but no indication as to why. Am I missing something? Is there something I should be checking?
Click to expand...
Click to collapse
Use Odin and flash the stock NC5.tar file, then take the OTA.
Virus!
Kaspersky reports this version of Towelroot is infected with an Android Virus. Try going to "towelroot.org" to get the official version.
sahaight said:
Kaspersky reports this version of Towelroot is infected with an Android Virus. Try going to "towelroot.org" to get the official version.
Click to expand...
Click to collapse
Tw roots your phone....of course its reported as malware.
muniz_ri said:
Tw roots your phone....of course its reported as malware.
Click to expand...
Click to collapse
Well yeah it is, but the guy posted a faulty website for towelroot. It's suppose to be https://towelroot.com/
WELP
muniz_ri said:
6. Power off then boot into "Download Mode" again.
7. Flash the I545_NG6_Stock_Kernel.tar.md5 also in Odin's PDA slot(AP in Odin v3.09+). Done!
Click to expand...
Click to collapse
So, I've followed the directions up to this point. One thing I did notice, you did say it would run wonky, but the version was noted as NG6 still after the NC5 write. TR still allowed me to root though, so I figured it wasn't really an issue. However, now that I've put my phone back in download mode, I'm attempting to write NG6 back onto my phone, and ODIN does the following
<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> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Any ideas what might be going on and how I could fix it?
Thanks
EDIT: I went ahead and reflashed NC5, Rerooted, rebooted, and attempted to Reflash NG6, It gave me the same issue, I rebooted my phone one last time, and attempted the reflash of NG6, This time it worked. Not sure what was holding it up the first time, but if you run into issues, try rebooting one more time.
SELinux Mode Changer
Can someone that has taken the NG6 update and rooted confirm whether or not SELinux Mode Changer continues to work allowing you to install the Safestrap.apk? Thx.
Before my phone didn't start and my Recovery says can't mount i had ilusion rom (http://forum.xda-developers.com/showthread.php?t=2363046) so i was looking for a solution and i found that i had to restore my phone to stock and i did that or at least try, starting it stuks on factoryfs.img now my phone is soft bricken then i tried again and it always stucks in factoryfs.img with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5 then i tried with I777UCMD8_I777ATTMD8_ATT 4.1.2 version and it stucks on Sbl.bin i was looking and some persons says that i need a pit file but i can't find it, i'm trying with Odin 1.74 1.83 3.09 fist time i tried was with odin v3.09.
PD: English is not my native language so sorry for bad spelling and thanks you very much if you can help me.
Alvarosl said:
Before my phone didn't start and my Recovery says can't mount i had ilusion rom (http://forum.xda-developers.com/showthread.php?t=2363046) so i was looking for a solution and i found that i had to restore my phone to stock and i did that or at least try, starting it stuks on factoryfs.img now my phone is soft bricken then i tried again and it always stucks in factoryfs.img with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5 then i tried with I777UCMD8_I777ATTMD8_ATT 4.1.2 version and it stucks on Sbl.bin i was looking and some persons says that i need a pit file but i can't find it, i'm trying with Odin 1.74 1.83 3.09 fist time i tried was with odin v3.09.
PD: English is not my native language so sorry for bad spelling and thanks you very much if you can help me.
Click to expand...
Click to collapse
You can find resources you need for the SGH-I777 in the Download Repository. (see the link in my signature) You will find a download link there for Odin3 v1.85, which is the recommended version for this phone. Any version of Odin should work, but if having issues it is a good idea to try v1.85.
It is very unlikely that you need to use a pit file. As a first step, please try the following. You may find that this solves the problem:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
If you get the phone going on Gingerbread, I would then flash I777UCMD8, which is the latest available stock, before you begin to customize again.
By the way, your English is very readable. Two suggestions: For "starting it stuks on factoryfs.img" you would write "it gets stuck on factoryfs.img" and for "now my phone is soft bricken" you would write "soft bricked".
Regards, and let us know if you get this resolved or need more help.
creepyncrawly said:
You can find resources you need for the SGH-I777 in the Download Repository. (see the link in my signature) You will find a download link there for Odin3 v1.85, which is the recommended version for this phone. Any version of Odin should work, but if having issues it is a good idea to try v1.85.
It is very unlikely that you need to use a pit file. As a first step, please try the following. You may find that this solves the problem:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
If you get the phone going on Gingerbread, I would then flash I777UCMD8, which is the latest available stock, before you begin to customize again.
By the way, your English is very readable. Two suggestions: For "starting it stuks on factoryfs.img" you would write "it gets stuck on factoryfs.img" and for "now my phone is soft bricken" you would write "soft bricked".
Regards, and let us know if you get this resolved or need more help.
Click to expand...
Click to collapse
first thank you very much for answering
when i try to install the kernel i can't pass this i'm like 20min by now and nothing(i'm using odin 1.85).
<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> zImage
<ID:0/003> NAND Write Start!!
and where can i find the gingerbread stock rom i can't find it
Alvarosl said:
and where can i find the gingerbread stock rom i can't find it
Click to expand...
Click to collapse
Skip to step 4. Follow steps 4, 5 & 6. You can get everything from the Download Repository. The stock gingerbread is the 5th item down, with the heading "I777UCKH7-CL503881 Stock Binaries:". The SBL Bootloader is the first item.
creepyncrawly said:
Skip to step 4. Follow steps 4, 5 & 6. You can get everything from the Download Repository. The stock gingerbread is the 5th item down, with the heading "I777UCKH7-CL503881 Stock Binaries:". The SBL Bootloader is the first item.
Click to expand...
Click to collapse
apology for not responding was busy these days and I could not download the complete parts,i always had an error and one more question before i try to do this i have to flash the tar file and bootloader cache.img, factoryfs.img, hidden.img, modem.bin and zImage or only the tar file in pda slot, i'll informs you when I can, thanks you soo much.
Alvarosl said:
apology for not responding was busy these days and I could not download the complete parts,i always had an error and one more question before i try to do this i have to flash the tar file and bootloader cache.img, factoryfs.img, hidden.img, modem.bin and zImage or only the tar file in pda slot, i'll informs you when I can, thanks you soo much.
Click to expand...
Click to collapse
Step 4. Flash the I777 UCKH7 sbl.tar in PDA
Step 5. Flash siyah-v2.6.14-att.tar in PDA
Step 6 Flash I777UCKH7-REV02-home-low-CL503881.tar.md5 in PDA
creepyncrawly said:
Step 4. Flash the I777 UCKH7 sbl.tar in PDA
Step 5. Flash siyah-v2.6.14-att.tar in PDA
Step 6 Flash I777UCKH7-REV02-home-low-CL503881.tar.md5 in PDA
Click to expand...
Click to collapse
i get succeed when i did step 4 but it didnt restart itself, now i cant turn it on again, i get a brick?
Can you get into recovery mode (power+both volume buttons)? Can you get into download mode (pull the battery and plug into the PC via USB cable, then power on)? Could be the battery died also. Too many variables, but really don't believe you've bricked it. Looks like you flashed the right file.
SteveMurphy said:
Can you get into recovery mode (power+both volume buttons)? Can you get into download mode (pull the battery and plug into the PC via USB cable, then power on)? Could be the battery died also. Too many variables, but really don't believe you've bricked it. Looks like you flashed the right file.
Click to expand...
Click to collapse
before when i conect my phone to my pc it power up now it dont, i tryed download mode and recovery the same doesnt work, i tryed to charge the batery with a charger external and the same i really think that this is dead, however i ll still trying to turn it on .
Hope isn't lost. Perhaps try running the program again, that is if the PC will recognize the device. I can't see how you could have bricked it using the same file many have installed for over 2 years!
Edit: that last statement wasn't meant to come off in a strong manner, was just trying to convey the validity of the .tar file. Also, did you flash the Siyah kernel as well? The device will give a black screen (with the appearance of not booting) if the wrong kernel/or none is installed.
SteveMurphy said:
Hope isn't lost. Perhaps try running the program again, that is if the PC will recognize the device. I can't see how you could have bricked it using the same file many have installed for over 2 years!
Edit: that last statement wasn't meant to come off in a strong manner, was just trying to convey the validity of the .tar file. Also, did you flash the Siyah kernel as well? The device will give a black screen (with the appearance of not booting) if the wrong kernel/or none is installed.
Click to expand...
Click to collapse
i think the bootloader is ok, that was not the problem, them about the kernel i try to install before install bootloader without succeed it stuck in wipe or something, then i restar in download mode and i install bootloader in pda with socceed byt i had the problem that it dont power up , i think maybe was a batery problem couse i dont know how much battery had the phone but i really dont know, i'm looking to sell it or change the mother board but i will try to do something before give up.