[How-To] Root I545VRUFNG6 - Verizon Samsung Galaxy S 4

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.

Related

Flashing CWM via ODIN succeeding, but recovery still boots into Android 3E Recovery

Edit: Problem Solved!
This problem is caused by an auto-restore script in Canadian ICS notes. When the phone boots up, it restores the recovery image to the stock Android recovery. To fix this problem, follow the link kindly supplied by zaptor99:
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
It worked for me!
Initial Post: So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Seems successful, no?
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
darknoon77 said:
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
Click to expand...
Click to collapse
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Wintersdark said:
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Click to expand...
Click to collapse
try TWRP or try to redownload CWM maybe you just got a bad zip
Bradl79 said:
try TWRP or try to redownload CWM maybe you just got a bad zip
Click to expand...
Click to collapse
How can I install TWRP on an unrooted phone without cwm installed? Is there an ODIN friendly tar kicking about? I looked but without success.
My zips are known good, though, used them to install CWM back on Gingerbread.
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Wintersdark said:
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Click to expand...
Click to collapse
I reverted back to Bell stock firmware and updated ics OTA.
I tried flashing CWM recovery a couple of times and I noticed the only time I can get into CWM is when I flash and press the volume up + down and the power button before my phone full reboots after the flash.
That way It works but right after the phone reboot for the first time after flashing CWM, it will not fo back into it.
Can anybody help us?
How can we try TWRP if we can't get into CWM?
Sent from my SGH-I717M using xda app-developers app
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
cwm 5.8.4.8 works flawlessly.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
Click to expand...
Click to collapse
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
It seems like its somehow reverting the restore partition on boot. i suspect it may be a scripted event "on next boot" after ODIN, so flashing another recovery then wouldnt help - the on next boot event happening again when you reboot.
However, ROM Manager would give you a chance to reflash recovery after that happens. Its a xhance, anyways. Seems to have worked for dark? I can't try until after work today.
Plz update me when u give Rom manager a try.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
Click to expand...
Click to collapse
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Agoattamer said:
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Click to expand...
Click to collapse
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Wintersdark said:
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Click to expand...
Click to collapse
It was pure stock Gingerbread. I was running an ATT leaked ICS version with CWM installed. But to get the Rogers update I used odin to restore the gingerbread version from here: http://forum.xda-developers.com/showthread.php?t=1657262
I did not install CWM or root before I used Kies to get the ICS update. But I see the difference now. I used Kies to get the update and you used OTA. Maybe if you went back to gingerbread and used Kies this time to get the update, it might fix your issue??
Any luck from Rom Manager?
I'm at at a wedding now so I won't be able to try it.
Sent from my SGH-I717M using xda app-developers app
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
That's fantastic! Thanks so much for the linkage there
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
Thanks Zaptor! it worked.
Finally, this gave me enough trouble.

SOLVED. stuck at samsung screen

Hey. i have looked in similar threads and i still cant find out how to fix it.
I just got a warranty phone and just updated it to ICS and followed the rooting steps for here http://forum.xda-developers.com/showthread.php?t=1483113
After using the pda.tar provided I Flashed the phone with odin 1.85 and on reboot the samsung galaxy I717 screen comes up the goes straight to the Samsung screen skipping the rogers logo and the start up clip.
then i found this thread http://forum.xda-developers.com/showthread.php?t=1840416 and i got the Rogers stock kernel-only odin pda tar. and flashed the phone again and on start up the telus logo comes up and just sits at that screen.
what do i need to do to get back to stock ics and re root?
Bakon420 said:
Hey. i have looked in similar threads and i still cant find out how to fix it.
I just got a warranty phone and just updated it to ICS and followed the rooting steps for here http://forum.xda-developers.com/showthread.php?t=1483113
After using the pda.tar provided I Flashed the phone with odin 1.85 and on reboot the samsung galaxy I717 screen comes up the goes straight to the Samsung screen skipping the rogers logo and the start up clip.
then i found this thread http://forum.xda-developers.com/showthread.php?t=1840416 and i got the Rogers stock kernel-only odin pda tar. and flashed the phone again and on start up the telus logo comes up and just sits at that screen.
what do i need to do to get back to stock ics and re root?
Click to expand...
Click to collapse
Here is the thread with all the tools required to get back to stock ics and rooting, http://forum.xda-developers.com/showthread.php?t=1740367
bigjoe2675 said:
Here is the thread with all the tools required to get back to stock ics and rooting, http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
wow pure life saver. thanks
Ok so I got the phone back to GB and the updated to ICS.
flashed with ClockworkMod Based Touch Recovery - 04/14/12
installed Superuser-i717-ICS-signed.zip.
then flashed flash_counter_reset_rogers.zip
so now im
custom binary download: NO
Current Binary: samsung offical
working perfect
Well done everyone! Bigjoe's Super Everything thread saved the day. . .again!
rangercaptain said:
Well done everyone! Bigjoe's Super Everything thread saved the day. . .again!
Click to expand...
Click to collapse
It's like the gnote Bible ....LOL
It really is amazing. Big thanks to big Joe!!
Bookmark worthy
gregsarg said:
It's like the gnote Bible ....LOL
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Might be a good name change The GNote Super bible Thread, GSbT, I'll use little b don't want to upset others.
But glad the gnote page helped, it's a thread of all the great work being done around our great community, not my work.
bigjoe2675 said:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Might be a good name change The GNote Super bible Thread, GSbT, I'll use little b don't want to upset others.
But glad the gnote page helped, it's a thread of all the great work being done around our great community, not my work.
Click to expand...
Click to collapse
:laugh:
yeh....may be hold off on that one....LOL
I have a similar problem but cannot NOT fix it
Bakon420 said:
Ok so I got the phone back to GB and the updated to ICS.
flashed with ClockworkMod Based Touch Recovery - 04/14/12
installed Superuser-i717-ICS-signed.zip.
then flashed flash_counter_reset_rogers.zip
so now im
custom binary download: NO
Current Binary: samsung offical
working perfect
Click to expand...
Click to collapse
Out of the many "stuck on samsung screen", Bakon420's post is mostly resembled of my problem. My Note is stuck at the "Samsung" screen. My hope is that someone can help me find the right thread and right way to fix it. I have read and continue reading. But the fear of keep bricking my Note to point of no return has prompted me to plead for help.
I have a Telus Galaxy Note SGH-i717, out of the box it came with Android 2.3.6. I updated it to Android 4.0.4 using the "update" feature in the "settings" of the phone.
I began rooting it using this method: http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/. After the method, I verifed that I had "superuser" app. When I used "root checker" app, it declared my Note was not rooted.
So again, I rooted it using another method at http://androidcritics.com/how-to-ro...7-on-android-2-3-6-gingerbread-and-4-0-4-ics/ . This method gave me the "stuck at "Samsung" screen.
On to xda-developers forum, I followed the threads and tried doing this: [STOCK ODIN] [AT&T, TELUS, Bell, Rogers] In case of brick...(http://forum.xda-developers.com/showthread.php?t=1506330). After using odin and Telus stock, Note was stuck at the "Telus" screen.
So I went on to this thread:
[ROOT] [AT&T, TELUS, Bell, Rogers] Pre-Rooted Kernel (flash via Odin) http://forum.xda-developers.com/showthread.php?t=1504218 and tried odin with the provided "pda.tar". Now it's back to "samsung" screen.
I have also tried this method: http://forum.xda-developers.com/showpost.php?p=28725010&postcount=10. Kies won't recognize it and won't do Tools>firmware upgrade and initialize.
All that happened within the 5 hours time frame last night. I feel exhausted. If you have the same problem and have resolved it, please point me a way. Thank you.
My Gosh man !!
Train wreck !!!
Sorry, I am willing to help you...as are the rest of the note family here...but you need to stop blindly flashing to the device...
It's so junked up with binary code, that it can't even crap...(rant off)
Okay Brother....
Do you have a recovery ??? As in CWM ??
If so...boot to the recovery, and wipe data, dalvik,....hell, basically everything 3 times.....(If not...then Odin push the recovery image to the device, so we can clean the garbage out of the system partition, and the boot partition)
You need a recovery to clean this phone up, then wipe all caches, data, battery stats...
Then, pull the battery....do not attempt to reboot, or you'll be stuck again...
Put the battery back in, then boot to download mode, and push the Odin .tar back to the device (the rom from the brick thread)
then reboot...
It may still give force closes etc.....thats because it still has junk in the system partition. but now we can boot into recovery and wipe again..
then on the second boot, you should be pretty clean..
those are the steps I'd use my friend...and no, i'm not pissed at you...it's just been a long azz day, and i know how you feel...g
gregsarg said:
My Gosh man !!
Train wreck !!!
Sorry, I am willing to help you...as are the rest of the note family here...but you need to stop blindly flashing to the device...
It's so junked up with binary code, that it can't even crap...(rant off)
Okay Brother....
Do you have a recovery ??? As in CWM ??
If so...boot to the recovery, and wipe data, dalvik,....hell, basically everything 3 times.....(If not...then Odin push the recovery image to the device, so we can clean the garbage out of the system partition, and the boot partition)
You need a recovery to clean this phone up, then wipe all caches, data, battery stats...
Then, pull the battery....do not attempt to reboot, or you'll be stuck again...
Put the battery back in, then boot to download mode, and push the Odin .tar back to the device (the rom from the brick thread)
then reboot...
It may still give force closes etc.....thats because it still has junk in the system partition. but now we can boot into recovery and wipe again..
then on the second boot, you should be pretty clean..
those are the steps I'd use my friend...and no, i'm not pissed at you...it's just been a long azz day, and i know how you feel...g
Click to expand...
Click to collapse
Okay. I will do it as I type this. First, boot in to recovery as in pressing vol. up and down and power, then let go power when it vibrates, but keep on pressing vol. up/down. It shows a 4g/lte Telus screen for about 2 secs. Now on to Android system recovery <3e>.
Now, using volume up/down to move highlight. Options are: reboot system now, apply update from external storage, wipe data/factory reset, wipe cache partition, and lastly apply update from cache. I don't see "dalvik" as an option. So, I'll do wipe data/factory reset, and wipe cache partition in that order 3 times. Okay, 3 times wipes. Now pull the battery...
Battery back in, boot to download mode. Screen says "ODIN MODE". product name SGH-i717D, custom binary download: YES (6 counts). Current binary: custom. Now load odin3 v1.85 on my computer, load up the "TELUS stock kernel-only odin pda tar" from the brick thread. Now plug in my usb cable to the phone and the computer. Only check boxes are "auto reboot", and "PDA". ID:COM box shows "0:COM6" in yellow color. Now , click start. ODIN Message:
<ID:0/006> Added!!
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Now the phone is rebooting and stuck at the "samsung" screen. The computer says "found new hardware Samsung Mobile MTP Device". Kies is loading automatically but not recognize any thing connected. Now booting to recovery to wipe data/factory reset and wipe cache again.
Now pull the battery out... back to recovery mode and reboot system now. It's still stuck in the samsung screen. !!! I feel like an idiot and maybe I am one and I don't know what else to do!
There is every indication that the kernel image you are using is not correct somehow...
And after reviewing the thread link you posted ....the affected user was able to repair the device by loading a rooted stock ICS build from flappjaxxx.
And since his roms contain the kernel image ....you can eliminate the need for a kernel by simply flashing his ICS rom.
But in order to do this ...you need the CLOCKWORKMOD recovery pushed to your device ....
And you currently have the stock 3e recovery. (Will not work)
So you need to push the CWM recovery to your device ....then flash the ICS build using your new recovery ....not Odin.
The only need for Odin at this point is to push the new recovery ...
Lets get that far ....and worry about the modem later...
Note : your device may contain a recovery script that forces the device to revert from a custom recovery, back to the 3e recovery.
Not all devices do.....
But if you do ....it's fixable ....and the fix can be found by a general search....but lets try the recovery push, and rom flash first using these steps ...
On PC .....
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Then move the downloaded rom to the download folder of your phones SD card.
Next :
Push the CWM recovery to your device using Odin.
If the device hangs at the samsung screen (it will ) don't pull battery...simply hold volume up and down, then power..
The device will start to vibrate every 2-4 seconds.....and after 3 vibration cycles ..release the power button but continue to hold the volume buttons.
The device will boot your new CWM recovery...
Then navigate to the "wipe data,factory reset " option and wipe the data.....then do the same for the cache and dalvik cache.
Then choose "install zip from SD card "...and flash the rom you placed to the device from the PC ..
Once the flash completely finishes .....reboot
If all went well ....you'll have ICS running ....
Let me know ..g
gregsarg said:
There is every indication that the kernel image you are using is not correct somehow...
And after reviewing the thread link you posted ....the affected user was able to repair the device by loading a rooted stock ICS build from flappjaxxx.
And since his roms contain the kernel image ....you can eliminate the need for a kernel by simply flashing his ICS rom.
But in order to do this ...you need the CLOCKWORKMOD recovery pushed to your device ....
And you currently have the stock 3e recovery. (Will not work)
So you need to push the CWM recovery to your device ....then flash the ICS build using your new recovery ....not Odin.
The only need for Odin at this point is to push the new recovery ...
Lets get that far ....and worry about the modem later...
Note : your device may contain a recovery script that forces the device to revert from a custom recovery, back to the 3e recovery.
Not all devices do.....
But if you do ....it's fixable ....and the fix can be found by a general search....but lets try the recovery push, and rom flash first using these steps ...
On PC .....
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Then move the downloaded rom to the download folder of your phones SD card.
Next :
Push the CWM recovery to your device using Odin.
If the device hangs at the samsung screen (it will ) don't pull battery...simply hold volume up and down, then power..
The device will start to vibrate every 2-4 seconds.....and after 3 vibration cycles ..release the power button but continue to hold the volume buttons.
The device will boot your new CWM recovery...
Then navigate to the "wipe data,factory reset " option and wipe the data.....then do the same for the cache and dalvik cache.
Then choose "install zip from SD card "...and flash the rom you placed to the device from the PC ..
Once the flash completely finishes .....reboot
If all went well ....you'll have ICS running ....
Let me know ..g
Click to expand...
Click to collapse
Thank you for your post. I will confirm the correct downloads and methods before actually trying them out. I am quite nervous because of previous failures. If this confirmation step seems overkill and rediculous to you, it is only because I am an idiot.
gregsarg said:
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Click to expand...
Click to collapse
means go to this thread: http://forum.xda-developers.com/showthread.php?t=1584576, download Odin from here: http://thinkleet.de/cwm/cwm-touch-i717-120414.tar.md5.
gregsarg said:
Push the CWM recovery to your device using Odin.
Click to expand...
Click to collapse
means using Odin3 1.85 adready on my PC to load cwm-touch-i717-120414.tar.md5 and flash it on my Note i717D. Is it correct?
gregsarg said:
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Click to expand...
Click to collapse
means , download this: i717-ICS-UCLE2: Credit and Thank you flappjaxxx. It is on the top and flle name implies it is the lastest version. Also this rom is the one to be moved to my SD card "download" folder. Is it correct?
Thank you. I have downloaded the files and await your confirmation.
Update: Sept. 26
I searched and found a thread that referred to CWM Recovery here: http://forum.xda-developers.com/showthread.php?t=1775263. The file in the mentioned thread is the same as the file you have indicated. So I downloaded it and pushed it to the phone, using Odin. Now I have booted in "CWM-based Touch Recovery v5.5.0.5". Run "wipe data/factory reset 3 times, wipe cache partition 3 times, and get in advanced to wipe Dalvik cache 3 times. Reboot recovery to go back to CWM Recovery main screen. Select "install zip from sdcard". Select "i717-ICS-UCLE2" from the sdcard. It took a few minutes and displayed "Flashing UCLE2 modem", then "Reboot Now", and lastly "Install from sdcard complete.", then return to the "Apply update from .zip file on SD card" screen of the CWM Recovery. Now reboot. There is no selection to reboot from this screen, so I just remove the battery, put it back in and restart the phone using the power button the normal way. The phone restarted with a screen "Samsung Galaxy Note, SGH-i717D", then onto the infamous white-on-blue "SAMSUNG" on the black background screen and stayed there.
Look like there is another problem somewhere else, caused by my second root attempt. For now, I will just sit tight to prevent further damage to the phone. Any thoughts that may explain and/or fix the problem is much appreciated.
Similar problem
Bakon420 said:
wow pure life saver. thanks
Click to expand...
Click to collapse
Hey good day I am currently having the same problem as you. I used odim and the pda file provided by link http://forum.xda-developers.com/showthread.php?t=1504218 however when phone restarts the screen is stuck on samsung. I would love to know what you did to fix this problem.
Thanks in advance
Take a look at the last post in that thread. That is a gingerbread kernel. I'm going to assume you're on ics. You'll have to install an ics kernel in recovery. Just make sure it's the correct kernel for your device and build. Just search and read. Also make sure to check the date on the thread. This thread was from August and the kernel thread you are referring to is from over a year ago. Good luck

[ODIN][TAR] Verizon SCH-I545 4.2.2 Emergency No-Wipe and Full-Wipe

DO NOT FLASH IF YOUR ON MDK AND WISH TO RETAIN YOUR CUSTOM RECOVERY! THIS WILL REMOVE THE LOKI EXPLOIT!
The credit of this exploit goes to the Dark Menace. If you would like to ask a question, please feel free to PM DarkMenace.​
Information:
Download Odin 3.07 here
Download: VRUAMDK No-Wipe.tar.zip
Download: VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5
Directions:
No-Wipe
1. Download and install if needed the Samsung USB v1.5x Drivers and reboot if prompted.(If phone isn't recognized you can try the v1.4x drivers.)
2. Download and extract ODIN v3.07.
3. Download and extract with winzip or my favorite winrar the VRUAMDK_NoWipe.tar.zip Factory Image (modified with No-Wipe).
4. Boot phone into ODIN mode (power off the phone, then press and hold Vol Down + Power then press Vol Up).
5. Connect your device using the provided USB cable and wait till the ID:COM port at Odin turns blue and you see “Added!!” on the message box. This shows that the connection between Odin and your device has been established.
6. Flash the VRUAMDK_NoWipe.tar.md5 Factory Image using ODIN v3.07 ***in PDA section only***.
7. You should now be able to boot back to Android and all your data should be intact exactly as it was.
Full Wipe ( AKA Emeregency Repair)
1. Download the full wipe files in the downloads section.
2. Download Odin 3.07
3. Download and install if needed the Samsung USB v1.5x Drivers (If phone isn't recognized you can try the v1.4x drivers.)
4. Turn off the device and boot it into Download/Odin Mode. Here is the method: press and hold the Volume Down+Home+Power buttons simultaneously for 2-3 seconds till you see a warning screen. Now press Volume Up key to enter Download Mode
5. Go to your Odin folder and launch Odin 3.07.
6. Connect your device using the provided USB cable and wait till the ID:COM port at Odin turns blue and you see “Added!!” on the message box. This shows that the connection between Odin and your device has been established
7. Now click on the PDA button, navigate to the firmware folder and select the file SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz
8. Then click on the PIT button, navigate to the PIT folder and select the file SCH-I545.pit
9. Make sure that Re-Partition and F Reset Time is selected on Odin. Also, do not forget to uncheck the Auto Reboot options
10. When you are sure that everything has been done correctly, click the Start button on Odin
11. Doing this will start the installation and it might take about 5-10 minutes to complete
12. When you see the PASS! message on Odin, disconnect the USB cable and close Odin
13. Now remove the back cover on your device and pull out the battery. Wait for about 1 minute and then place the battery back to its place.
14. Boot your Galaxy S4 into Android System Recovery mode: hold Volume Up+Home+Power keys together till the screen turns up and the Samsung logo blinks twice. Then release the Power button but keep Volume Up and Home keys pressed till you see the recovery menu. In recovery mode use the volume keys to scroll and power button to select options
15. Go to “wipe data/factory reset” option and wipe it
16. Then “wipe cache partition”
17. Finally, go to “reboot system now” and select it
18. Your Galaxy S4 will boot now. Usually, it takes a longer time than usual to boot the device, so wait patiently till you see the Welcome Set Up screen. You know well what to do here.
Can I use the No Wipe on my phone as is on MJ7? I have also blocked OTA and Frozen all Knox software. I have also put on the WiFi Hotspot toggle with other Toggles. Will I be able to use the NO WIPE version as is or do I need to undo all of this stuff first?
After you have done the NO WIPE will it retain root, as well as Safestrap 3.71?
Sorry for the shot gun of questions.
swc2001 said:
Can I use the No Wipe on my phone as is on MJ7? I have also blocked OTA and Frozen all Knox software. I have also put on the WiFi Hotspot toggle with other Toggles. Will I be able to use the NO WIPE version as is or do I need to undo all of this stuff first?
After you have done the NO WIPE will it retain root, as well as Safestrap 3.71?
Sorry for the shot gun of questions.
Click to expand...
Click to collapse
If you're on MJ7, you can't use these. They're the MDK build, android 4.2.2. Your phone already has android 4.3, and the bootloader won't allow you to downgrade.
k1mu said:
If you're on MJ7, you can't use these. They're the MDK build, android 4.2.2. Your phone already has android 4.3, and the bootloader won't allow you to downgrade.
Click to expand...
Click to collapse
Not if he's running all of those on a modded rom. I had all of that stuff on my MK2 rom. Although he couldn't have downgraded, he seems to be concerned with making absolutely certain that Verizon has as little control as possible.
Sent from my SCH-I545 using Tapatalk
I upgraded to VRUFNC5 and wow do I want to go back so I can get root again. I saw your earlier post about not being able to since the bootloader will not allow to downgrade.
My question is, won't Odin put a new image on the phone, everything included? Or does Odin just put a new system image on the phone and the bootloader is separate?
Thanks for lesson in advance....
I am such a moron.... lol. I somehow thought this was to upgrade to kitkat. Derp!
Well is there something like this that will allow us to upgrade to kitkat.... ie no wiping
Sent from my SCH-I545 using Tapatalk
kfres39389 said:
Not if he's running all of those on a modded rom. I had all of that stuff on my MK2 rom. Although he couldn't have downgraded, he seems to be concerned with making absolutely certain that Verizon has as little control as possible.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If he's running a modded ROM, he's running the MDK bootloader. Or, Safestrap. These are not safestrap-compatible.
k1mu said:
If he's running a modded ROM, he's running the MDK bootloader. Or, Safestrap. These are not safestrap-compatible.
Click to expand...
Click to collapse
Point taken. I had Safestrap.
Sent from my SCH-I545 using Tapatalk
Full wipe download keeps crashing.
Any mirrors?
ymDroid said:
Full wipe download keeps crashing.
Any mirrors?
Click to expand...
Click to collapse
+1 in desperate need!
Sent from my SCH-I545 using Tapatalk
R3CKL355 said:
+1 in desperate need!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Check out Surges thread here.
http://forum.xda-developers.com/showthread.php?t=2735172
I'm on my phone and could be missing something in this thread, and don't want to give you the wrong files.
These are the NC5 wipe Odin Tars that I uploaded as a torrent, because I kept getting errors when I was extracting the archives. I have both the Wipe and Non-Wipe files in it. https://www.demonoid.ph/files/details/3024298/48033544/
tried to upgrade a rom, no wifi , bad problem and lost
Android , 4.3 , I545VRUFNC5 , KERNEL 3.4.0 BUILD JSS15J.1545VRUEMK2
using this
Downgrade_I545VRUEMK2_old , JFLTE_USA_VZW_16G.pit , plus this VRUFNC5_Rooted_Stock-v2 , to get me where i am ...
but still no WiFi
this all happened after trying to upgrade a rom ... i ended up with a rom and no wifi , and since im not on a contract , i need the WiFi i tried gogolies-wififix-VZW-FN2-NC2-w-modules-SS.zip , but no go
so im lost now i once had
VZW S4 SCHi545, Android 4.4.2, Baseband NC5, Kernel 3.4.2
I rooted using towelroot, installed Supersu, terminal, busybox and safestrap 3.7.2
Rooting process went flawlessly. Used safestrap to flash Hyperdrive 17.1, which also went flawlessly.
Wifi did not work, which I expected because I read before flashing.
I downloaded gogolies NC2 fix, NC5 fix, VZW modules, etc etc etc. Tried numerous ways top get them installed without success.
So now I have 2 acceptable options...
#1 get wifi working
#2 revert to my backup
Currently, I have 2 issues, because I can't do either of those things above.
#1 Safestrap won't run (details follow)
#2 - Every time I try to install any of the gogolies zips I get # footer is wrong and # signature verification errors. Unknown sources is enabled, verify apps is off (I tried with it on and off). I'm using CWM from the Hyperdrive reboot to recovery menu to install the zips, because #1...
ive tired this and other tars ive forgotten which but this one did not work
Error
When Verizon SCH-I545 put 562 219 4.2.2 Stock Restore.tar.md5 in PDA, get this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
Theericgames said:
When Verizon SCH-I545 put 562 219 4.2.2 Stock Restore.tar.md5 in PDA, get this:
Click to expand...
Click to collapse
The MD5 is incorrect. It means it's a bad download. Redownload.
Is this for mdk2?
Thanks

[Q] question about upgrading to NC5

I am currently on MJ4 jellybean (rooted) and I want to upgrade to NC5 for the wifi calling. Can I simply use odin V3.09 and install this tar and be done?
Download Android 4.4.2 NC5 Firmware for Sprint Note 3 SM-N900P [LATEST][Wifi-Calling]
Does this keep root or will I have to unroot my phone again after running this tar in odin?
If this is incorrect, can someone please tell me how to upgrade to NC5 from Mj4??? Thanks.
randyreed1971 said:
I am currently on MJ4 jellybean (rooted) and I want to upgrade to NC5 for the wifi calling. Can I simply use odin V3.09 and install this tar and be done?
Download Android 4.4.2 NC5 Firmware for Sprint Note 3 SM-N900P [LATEST][Wifi-Calling]
Does this keep root or will I have to unroot my phone again after running this tar in odin?
If this is incorrect, can someone please tell me how to upgrade to NC5 from Mj4??? Thanks.
Click to expand...
Click to collapse
Here is 1 method : [HOW-TO] Update to 4.4.2 NAB & NC5 w/Root from MJ4 Rooted without triggering Knox 0x1
and this one
[Stock ROM] Odin flashable N900PSPTDNH7 (says NH7 but it has the older tars as well)
jdelano said:
Here is 1 method : [HOW-TO] Update to 4.4.2 NAB & NC5 w/Root from MJ4 Rooted without triggering Knox 0x1
and this one
[Stock ROM] Odin flashable N900PSPTDNH7 (says NH7 but it has the older tars as well)
Click to expand...
Click to collapse
Well, I tried to install recovery first using the TWRP Manager app and when I choose reboot into recovery it will start to reboot and when it says "set Warranty Bit: recovery" (in yellow), it will not do anything. I then downloaded the 2.8 recovery tar file and tried to install it in odin and when I reboot into recovery it will get to the ""set Warranty Bit: recovery" (in yellow and still not do anything. The only way I can reboot my phone from there is to pull the battery, hold the power down, power and home button, then choose reboot phone.
How do I fix this problem??
randyreed1971 said:
Well, I tried to install recovery first using the TWRP Manager app and when I choose reboot into recovery it will start to reboot and when it says "set Warranty Bit: recovery" (in yellow), it will not do anything. I then downloaded the 2.8 recovery tar file and tried to install it in odin and when I reboot into recovery it will get to the ""set Warranty Bit: recovery" (in yellow and still not do anything. The only way I can reboot my phone from there is to pull the battery, hold the power down, power and home button, then choose reboot phone.
How do I fix this problem??
Click to expand...
Click to collapse
So you Odin'd to NAB and took OTA to NC5 or did you go right to NH7?
In any event after Odin'g to stock reboot your phone and let it load 100% stock
Then put SuperSU214.zip to your SD Card
turn the phone off
boot to download mode
Odin Philz Recovery (I prefer that sorry)
don't auto reboot.
when its finished and passed, hold the boot to recovery buttons - the phone will reboot into recovery
flash the supersu214.zip (for root)
reboot phone and let it boot
you now have stock root
good luck
jdelano said:
So you Odin'd to NAB and took OTA to NC5 or did you go right to NH7?
In any event after Odin'g to stock reboot your phone and let it load 100% stock
Then put SuperSU214.zip to your SD Card
turn the phone off
boot to download mode
Odin Philz Recovery (I prefer that sorry)
don't auto reboot.
when its finished and passed, hold the boot to recovery buttons - the phone will reboot into recovery
flash the supersu214.zip (for root)
reboot phone and let it boot
you now have stock root
good luck
Click to expand...
Click to collapse
No, the only thing I have done was try to update TWRP from 2.6.3.7 to TWRP 2.8.......for some reason when I try and update the recovery it will not go into recovery, it simply does nothing after the ""set Warranty Bit: recovery" (in yellow) is displayed.
Do I need to update my TWRP recovery or can I just flash the stock NH7 tar in 3.07 odin?
Can I flash the N900PSPTDNH7 tar file in odin 3.07 with my TWRP 2.6.3.7 recovery and be OK???
randyreed1971 said:
No, the only thing I have done was try to update TWRP from 2.6.3.7 to TWRP 2.8.......for some reason when I try and update the recovery it will not go into recovery, it simply does nothing after the ""set Warranty Bit: recovery" (in yellow) is displayed.
Do I need to update my TWRP recovery or can I just flash the stock NH7 tar in 3.07 odin?
Can I flash the N900PSPTDNH7 tar file in odin 3.07 with my TWRP 2.6.3.7 recovery and be OK???
Click to expand...
Click to collapse
Ah, you can't use the newer recoveries with older firmware/bootloader.
You'll have to just odin NH7, follow the steps I gave you and you'll be back at stock rooted.
It will be a good idea to wipe factory reset though, after booting 100% stock, boot to stock recovery and do that then turn the phone off and start the process of putting NH7 (you really should start 100% fresh because you're moving up 3 upgrades)
jdelano said:
Ah, you can't use the newer recoveries with older firmware/bootloader.
You'll have to just odin NH7, follow the steps I gave you and you'll be back at stock rooted.
It will be a good idea to wipe factory reset though, after booting 100% stock, boot to stock recovery and do that then turn the phone off and start the process of putting NH7 (you really should start 100% fresh because you're moving up 3 upgrades)
Click to expand...
Click to collapse
Thanks, I got it to work. I actually didnt do a wipe (I FORGOT) but when it booted up everything was like I had it before upgrading and its working perfectly.
Now to do a backup and find a good ROM.
randyreed1971 said:
Thanks, I got it to work. I actually didnt do a wipe (I FORGOT) but when it booted up everything was like I had it before upgrading and its working perfectly.
Now to do a backup and find a good ROM.
Click to expand...
Click to collapse
yw, glad to hear that!

Need help with soft bricked i777

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.

Categories

Resources