AT&T'ers: DO NOT FLASH MY RECOVERY.TAR.MD5 FILE. IT WAS CREATED FROM AN I337M FIRMWARE BASEBAND vI337MVLUAMDJ, AND I AM NOT SURE WHAT FLASHING IT WOULD DO TO YOUR PHONE.
WARNING: Follow these instructions at your own risk! I take no responsibility for your phone, or any damage to it, as a result of anything in this guide!
Note: Part of this method entails flashing a recovery.tar.md5 file through Odin. To get this file, I pulled the Samsung stock recovery straight from the latest Rogers firmware and repackaged it as an Odin flashable tar.md5 file. I flashed this through Odin on my phone, and it replaced TWRP with the Samsung Stock Recovery without a problem. I am on Rogers, I assume it will work for other i337M carrier variants with baseband version: I337MVLUAMDJ, but I cannot guarantee it as I have not tested it. Flash at your own risk.
My instructions assume anyone who flashes this in ODIN knows how get into Download Mode, has the correct drivers installed, and has flashed in ODIN before. If not, please search for the many guides on how to do this.
Now that the warnings are out of the way, here is the procedure:
This method allows you to restore your phone without having to do a full firmware Odin flash. I don't know about you guys, but I don't like to wait the 20 mins for the full Odin restore. Call me impatient, but time is my most valuable resource these days! Here are the steps:
Step #1: Full wipe of custom rom in recovery. Restore stock rom from nandroid.
Step #2: Flash Stock Recovery File in Odin:
I used Odin3 v3.07 to successfully flash this. To flash it in ODIN, click PDA, select the recovery.tar.md5 (Download It Here). I flashed successfully with only "Auto Reboot" and "F. Reset Time" selected. MAKE SURE "RE-PARTITION" IS NOT SELECTED.
When done flashing in Odin, reboot into recovery and make sure you have the stock version. There will be an android lying on his back with a red triangle above him. If your phone does not boot into recovery doing the volume up/power/home button combo (happened to me), either use adb reboot recovery (only other option when root is uninstalled), or goo manager, quick re-boot or other app with a recovery reboot option.
Flashing this in Odin will increase your flash counter (Mine was already at 1 from TWRP installation). No big deal, see step #3 below.
Step #3: Open the latest version of Triangle Away (v2.90) and reset your flash counter to 0. Worked perfectly on my phone. Note: Device status will remain at "custom", even though Triangle Away may show it as official.
Step #4: Make a backup of root using Voodo OTA RootKeeper (Free app from Google Play.)
Step #5: Update your Titanium Backups as a factory reset will be required in a later step.
Step #6: Open Supersu and click the "Full Unroot" option.
Step #7: Go into your root explorer app, look in system/xbin, and make sure you delete su and busybox if they are still there.
Step #8: Reboot you phone normally.
Step #9: Go into options/about device/status and check your device status. If it says "Official", you got lucky and are done. This is unlikely, but worth the check.
Step #10: Reboot into the stock recovery. Select factory reset by using the volume keys to toggle the selection, and power button to select. Once this is done, stay in the Stock recovery and select wipe cache partition. It should reboot after this operation.
Step #11: After reboot, your device status should read official. If not, double check that you followed each step above. Still if not, I would suggest you try flashing the full firmware through Odin. This worked for me, I hope it works for you, but I have not tested beyond this. Make sure to reboot again and check your device status once more, just to be sure.
Step #12: If you are returning your device, you are done.
Step #13: Open Voodo OTA RootKeeper and select restore root. Close Voodo. Install Supersu from Google Play, install binaries, and you should be rooted again.
Step #14: Check your device status after you root. It should still say official (mine did). To be extra safe, reboot and check device status again (mine still said official).
That should be it. You are now back on rooted stock with the ability to get ota's.
Just to clarify for all the people who still didn't pay complete attention to the OP, THIS IS FOR CANADIAN VARIANTS ONLY!
DO NOT FLASH ON YOUR US AT&T GS4! DO NOT! DO NOT! DO NOT!
That is all! :good:
Big, big thanks my friend! I've flashed the recovery file in a Telcel phone (Mexico, obv i337m) and it came back to life! :highfive:
Just exactly what I was looking for..
Thanks!
Sent from my SGH-I337M using xda app-developers app
David Dee said:
AT&T'ers: DO NOT FLASH MY RECOVERY.TAR.MD5 FILE. IT WAS CREATED FROM AN I337M FIRMWARE BASEBAND vI337MVLUAMDJ, AND I AM NOT SURE WHAT FLASHING IT WOULD DO TO YOUR PHONE.
WARNING: Follow these instructions at your own risk! I take no responsibility for your phone, or any damage to it, as a result of anything in this guide!
Note: Part of this method entails flashing a recovery.tar.md5 file through Odin. To get this file, I pulled the Samsung stock recovery straight from the latest Rogers firmware and repackaged it as an Odin flashable tar.md5 file. I flashed this through Odin on my phone, and it replaced TWRP with the Samsung Stock Recovery without a problem. I am on Rogers, I assume it will work for other i337M carrier variants with baseband version: I337MVLUAMDJ, but I cannot guarantee it as I have not tested it. Flash at your own risk.
My instructions assume anyone who flashes this in ODIN knows how get into Download Mode, has the correct drivers installed, and has flashed in ODIN before. If not, please search for the many guides on how to do this.
Now that the warnings are out of the way, here is the procedure:
This method allows you to restore your phone without having to do a full firmware Odin flash. I don't know about you guys, but I don't like to wait the 20 mins for the full Odin restore. Call me impatient, but time is my most valuable resource these days! Here are the steps:
Step #1: Full wipe of custom rom in recovery. Restore stock rom from nandroid.
Step #2: Flash Stock Recovery File in Odin:
I used Odin3 v3.07 to successfully flash this. To flash it in ODIN, click PDA, select the recovery.tar.md5 (Download It Here). I flashed successfully with only "Auto Reboot" and "F. Reset Time" selected. MAKE SURE "RE-PARTITION" IS NOT SELECTED.
When done flashing in Odin, reboot into recovery and make sure you have the stock version. There will be an android lying on his back with a red triangle above him. If your phone does not boot into recovery doing the volume up/power/home button combo (happened to me), either use adb reboot recovery (only other option when root is uninstalled), or goo manager, quick re-boot or other app with a recovery reboot option.
Flashing this in Odin will increase your flash counter (Mine was already at 1 from TWRP installation). No big deal, see step #3 below.
Step #3: Open the latest version of Triangle Away (v2.90) and reset your flash counter to 0. Worked perfectly on my phone. Note: Device status will remain at "custom", even though Triangle Away may show it as official.
Step #4: Make a backup of root using Voodo OTA RootKeeper (Free app from Google Play.)
Step #5: Update your Titanium Backups as a factory reset will be required in a later step.
Step #6: Open Supersu and click the "Full Unroot" option.
Step #7: Go into your root explorer app, look in system/xbin, and make sure you delete su and busybox if they are still there.
Step #8: Reboot you phone normally.
Step #9: Go into options/about device/status and check your device status. If it says "Official", you got lucky and are done. This is unlikely, but worth the check.
Step #10: Reboot into the stock recovery. Select factory reset by using the volume keys to toggle the selection, and power button to select. Once this is done, stay in the Stock recovery and select wipe cache partition. It should reboot after this operation.
Step #11: After reboot, your device status should read official. If not, double check that you followed each step above. Still if not, I would suggest you try flashing the full firmware through Odin. This worked for me, I hope it works for you, but I have not tested beyond this. Make sure to reboot again and check your device status once more, just to be sure.
Step #12: If you are returning your device, you are done.
Step #13: Open Voodo OTA RootKeeper and select restore root. Close Voodo. Install Supersu from Google Play, install binaries, and you should be rooted again.
Step #14: Check your device status after you root. It should still say official (mine did). To be extra safe, reboot and check device status again (mine still said official).
That should be it. You are now back on rooted stock with the ability to get ota's.
Click to expand...
Click to collapse
Finally someone uploads a stock recovery file for I337M. Thanks! Just the file i need to change back from custom recovery.
I also have a question, if you are running stock carrier rom, do i need to run triangle away when i have custom recovery installed with no yellow triangle?
I used TRIANGLEAWAY.APK Worked for me the 3 or 4 times I've had to use it. Due to being in a hurry and forgetting to LOKI. You just have to follow the in Apk. instructions to a "T" And make sure you do it while you have a ROM based off of your phone "I337" "I9505". Etc. Its on the play store. Works great. I can't guaranty that but its never failed me.
Playstore TRIANGLEAWAY LINK:
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Sent from my SGH-I337 using Xparent Skyblue Tapatalk 2
Thank you very much, i go back and forth between roms and this guide saved me when i thought i almost bricked my phone
I imagine there is no Canadian gs4 separate forum, that's why you post it here in the att forum?.
Just asking because I'm pretty sure most people will assume your ROM is for the att variant since the forum says att galaxy s4.
Not trying to be an ass or anything like it.
Sent from my Nexus 7 using xda app-developers app
@alfmetal
Yes, we don't have our own forum, but that's why his thread says I337M.
And yes, this is an awesome tool. I've used it a few times.
2ve6ay
oh ok cool
so the M means from CANADA? or something like that?
i was thinking it meant something like MOBILE?
Related
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
I have a samsung galaxy tab 2 10.1 gt-p5113
I tried to root it before, but got as far as flashing the recovery software ( can't find the thread I used to do this but I think it involved odin)
anyways when I flashed the recovery software the tab got stuck at the boot screen and I though it was bricked but after reflashing and restarting it a few times it worked again....needless to say I didn't have the balls to try rooting it after that.....
now when I search for software updates it says my device has been modified and cannot update ( it still is NOT rooted )
Is this because of the recovery software?...which as far as I can tell hasn't been properly installed cause I can't find any evidence of it on my tab, even when i hold down the power and volume button and the recovery software is supposed to show up.
and how do i undo it so that I can get updates? I just want the stock software back. will a factory reset do the trick?
No, the instant you attempted to install CWM, a bootloader data value changed that made your device always read as modified. There are three ways to get to Jelly Bean from where you are.
1. Root and run TriangleAway. This app will reset the bootloader counter, so you should be able to upgrade normally.
2. Install CWM via ODIN and install a custom JB-based ROM. You will need to root first if you want to keep your data via Titanium Backup.
3. ODIN a JB-based ROM for your carrier/region. Same deal as above with rooting and keeping your data.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
No, the instant you attempted to install CWM, a bootloader data value changed that made your device always read as modified. There are three ways to get to Jelly Bean from where you are.
1. Root and run TriangleAway. This app will reset the bootloader counter, so you should be able to upgrade normally.
2. Install CWM via ODIN and install a custom JB-based ROM. You will need to root first if you want to keep your data via Titanium Backup.
3. ODIN a JB-based ROM for your carrier/region. Same deal as above with rooting and keeping your data.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I have this same exact problem. I have tried to un-root but nothing happned. I have tried to update via Kies and nothing happened. Should I try to root again? I just want to get the 4.2.2 update.
If you want your device's status to read "official",
1. Root your device (I prefer Chainfire autoroot)
2.a) Run triangle away, reset your bin (flash) counter. Now your bootloader will say 0 counts.
2.b) As for the device status (in about device), there's a button just under "reset" in triangle away application, tap it and reboot. Your device status will now be "official"
3. (Optional) Go to your Superuser application, tap cleanup and unroot (if available)
Now you're unrooted, and running official firmware. You can use OTA anytime.
I recently purchased a Galaxy S Blaze which I now need to return, but before I do so I want to restore it to its original configuration. The device is currently rooted, and ClockworkMod Recovery is installed. I had installed a custom ROM called Cyanogenmod 10.0.0, but then I eventually restored a backup, via CWM Recovery, of my original Gingerbread 2.3.6 load (baseband version T769UVLF5). Also, I have backed up my contacts, etc.
From what I understand, I need to unroot the phone, reset the flash counter, remove CWM and reinstall the stock recovery utility. And after researching the individual steps of this process, I'm still unclear on some of the details. So here are my questions:
1. In what order must these steps be performed, and is there anything else I need to do?
2. Since I have restored a backup of the original firmware, do I need to perform the additional step of downloading and installing a stock firmware such as SGH-T769-UVLB7-k0nane.7z in order to unroot the phone?
3. Where do I obtain the stock recovery with which to replace CWM, and how do I install it?
I'm still new to all of this, and I want to make sure I do this right!
http://forum.xda-developers.com/showthread.php?t=1591601
Sent from my SGH-T769 using xda premium
I followed these instructions to reset the flash counter:
http://forum.xda-developers.com/showthread.php?t=1955273
After the reset successfully completed (from within CWM), I rebooted into download mode and installed the stock ROM SGH-T769-UVLB7-hitsquad.tar, as explained here:
http://forum.xda-developers.com/showthread.php?t=1591601
Once again, I rebooted into download mode, which displayed this information:
CUSTOM BINARY DOWNLOAD: YES(2 counts)
CURRENT BINARY: CUSTOM
What did I do wrong?
Specifically, I don't understand how to reset the counter as the last step. (Because resetting the counter requires CWM, and CWM requires root access.)
You don't need root to have cwm, just Odin it.
Romman0 said:
You don't need root to have cwm, just Odin it.
Click to expand...
Click to collapse
Thanks, Romman0-- I didn't realize that.
Just to follow up, my problem was that I was flashing with the "stock" ROM SGH-T769-UVLB7-hitsquad.tar. When I downloaded and installed an "official" ROM from SamMobile, everything worked perfectly.
I appreciate everyone's help!
Method# 1: This "Keep Root" method uses a modified version of the official NB1 to NC1 OTA Update.zip to upgrade while maintaining User Data and Root Access! The file is flashed in Safestrap and the end result is a 100% Stock, Rooted, NC1 Device. Proceed at your own risk!
**Closing my thread now that a direct rooting method is available. Thanks to @kevp75 and @loganfarrell for all of the support provided to me and others in this thread!**: http://forum.xda-developers.com/showthread.php?t=2783157
**Important Notice**: If you are currently on factory stock, unrooted NB1 or NC1 follow the instructions in Post# 3!:
Donations Welcome!
**Prerequisite** You must be on a 100% Stock NB1 system, except for root and safestrap, before proceeding with this method! The update will fail if any NB1 system files have been modified or deleted, e.g. thru Xposed, flashing Tether AddOn.zip, etc. You must first restore the stock files or flash the I337UCUFNB1_100%_Stock_Rooted_ROM. Or, instead update to NC1 by flashing the I337UCUFNC1_100%_Stock_Rooted_ROM from Post# 3 below.
Here it is: I337_NB1toNC1_KeepRoot_OTA.zip
And here: I337_NB1toNC1_KeepRoot_OTAwBL.zip (This version contains the NC1 bootloader, MK2 bootloader users will not be able to flash back to factory stock MK2 after flashing).
1. Place the I337_NB1toNC1_KeepRoot_OTA.zip in the root of your ext sdcard.
2. Make certain that you have installed the latest Safestrap-JFLTE-3.72-kk-B01.apk.
3. Boot into Safestrap recovery but Do Not Wipe!.
4. Flash the NB1toNC1_KeepRoot_OTA.zip in the "Stock Slot." Once flashing is complete press "Home" and reboot into "Download Mode".
5. Last, flash the I337_NC1_Stock_Kernel in Odin's PDA slot(AP in Odin v3.09+).
Once complete the phone will reboot then "optimize apps" before completely rebooting. Done!
Known Issue: Safestrap.apk will force close after updating to NC1 using this method, however Safestrap recovery will continue to function. Optional: To manually uninstall safestrap recovery use Es File Explorer to delete system/etc/safestrap and system/bin/e2fsck, then rename system/bin/e2fsck.bin to e2fsck (save these files if you wish to manually reinstall Safestrap at a later time).
I337UCUFNC1_100%_Stock_Rooted_TetherAddOn
Instructions:
1. After flashing and booting into I337UCUFNC1_100%_Stock_Rooted_ROM or I337_NB1toNC1_KeepRoot_OTA.zip,
2. Place the AddOn in ext sdcard.
3. Reboot into Safestrap recovery and flash the AddOn in Stock Slot (Do Not Wipe Prior to Flashing)
4. Reboot. Done!
Extras (No need to flash, provided as a courtesy).
Flash in PDA slot in Odin (AP in Odin v3.09+)
I337_NC1_Stock_Modem
I337_NC1_Stock_Recovery
I337UCUFNC1_100%_Stock_Rooted_ROM
Method# 2: The following is not a root method in the "traditional" sense, e.g. Saferoot, Kingo. This is a workaround to our inability to root KitKat 4.4.2. However the end result is a Fully Functioning 100% Stock, Rooted, NC1 Device. Proceed at Your Own Risk!.
**Note**: The process below has been proven to work without exception when the instructions are followed to the letter. Should you run into trouble please consider re-reviewing the instructions to identify your error before requesting assistance. Thank you.
Here it is: I337UCUFNC1_100%_Stock_Rooted_ROM
And here: I337UCUFNC1_100%_Stock_Rooted_ROMwBL (This version contains the NC1 bootloader, MK2 bootloader users will not be able to go back to factory stock MK2 after flashing).
1. Place the I337UCUFNC1_100%_Stock_Rooted_ROM in the root of your ext sdcard.
*2. Download the I337_Downgrade_to_MK2 file, extract the .tar and flash in PDA slot in Odin(AP in Odin v3.09+) to obtain semi-functioning(no-wifi) MK2.
3. Use your favorite root method to root MK2, e.g. Saferoot, Kingo Root App, then install the latest Safestrap-JFLTE-3.72-kk-B01.apk.
4. Boot into Safestrap recovery, perform an "Advanced Wipe" and wipe everything except ext sdcard.
5. Flash the ROM zip in the "Stock Slot." Once complete press "Home," then reboot into "Download Mode".
6. Flash the I337_NC1_Stock_Kernel in PDA slot in Odin(AP in Odin v3.09+).
*MK2 users can skip Step# 2.
Once complete the phone will reboot and pause on the white AT&T splash screen for about 1-2 minutes before completely booting into the ROM. Done!
- It's recommended that you use Safestrap's Backup/Restore function to backup and restore User Data prior to and after flashing the ROM. Make sure and thank @loganfarrell for discovering this very useful feature.
- In general, to flash a different 4.4.2 Safestrap Custom ROM after flashing this ROM reboot into Safestrap recovery, perform an advanced wipe, and wipe everything but ext sdcard. Then flash the new ROM in the "Stock Slot" and reboot (Refer to the other ROM's dedicated thread for any additional requirements or for assistance. Please limit the discussion in this thread to the 100%_Stock_Rooted_ROM and the KeepRoot OTA zip).
Known Issues: None!
I337UCUFNC1_100%_Stock_Rooted_TetherAddOn
Instructions:
1. After flashing and booting into I337UCUFNC1_100%_Stock_Rooted_ROM or I337_NB1toNC1_KeepRoot_OTA.zip,
2. Place the AddOn in ext sdcard.
3. Reboot into Safestrap recovery and flash the AddOn in Stock Slot (Do Not Wipe Prior to Flashing)
4. Reboot. Done!
reserved2
I am running iB4STiD's KangKat 6.1 is it safe to flash the new modem in ODIN?
neverends said:
I am running iB4STiD's KangKat 6.1 is it safe to flash the new modem in ODIN?
Click to expand...
Click to collapse
Yes, there shouldn't be any issues with that.
@muniz_ri Nice Job My Friend! :good: Let's all hit the Thanks Button for and awesome job Here!
If I'm already on rooted NB1 would it be worth it to upgrade or should I just stick on NB1? not sure what the differences are..
Rhymey said:
If I'm already on rooted NB1 would it be worth it to upgrade or should I just stick on NB1? not sure what the differences are..
Click to expand...
Click to collapse
Likely placebo but NC1 seems slightly smoother.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm still running stock rooted MDL. Can I use one of these to flash up to NC1 just using CWMRecovery? I just want to make sure I don't lose my sweet MDL bootloader!
Deadly Venom v3.0.2 AT&T KitKat 4.4.2 SAFESTRAP|UCUFNC1|ODEXED Is Live and Running, UPLOADING SAFESTRAP EDITION Make sure you hit The Thanks button on here Big Thanks to @muniz_ri for sharing his Dump NC1 :good:
When the hell did I miss the NC1 modem???
That's all I care about. I'm using mdl just so I can access service mode.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Installed this and all is working flawlessly. Once again, the fantastic work of @muniz_ri is delivered quickly and is a work of perfection.
muniz_ri said:
Likely placebo but NC1 seems slightly smoother.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Awesome job! As always!!! Thanks, @muniz_ri !
Just flashed worked great thanks @muniz_ri !! It does seem to have more butter
@muniz_ri Everything works fabulous. Just unclear on one thing....When I go to manually uninstall SS, I was able to delete the system/etc/safestrap folder and I saw the file system/bin/e2fsck. But I could never find the system/bin/e2fsck.bin. I tried to uninstall and reinstall Safestrap and it will load but will not give me the recovery option. Any assistance would be appreciated! Thanks in advance!
When loading the full rom (I337UCUFNC1_100%_Stock_Rooted_ROM) does that also take care of updating the stock radio and stock recovery?
Sorry if this is already spelled out somewhere, I just don't see it.
Thanks.
muniz_ri said:
The following is not a root method in the "traditional" sense, e.g. Saferoot, Kingo. This is a workaround to our inability to root KitKat 4.4.2. However the end result is a Fully Functioning 100% Stock, Rooted, NC1 Device. Proceed at Your Own Risk.
Here it is: I337UCUFNC1_100%_Stock_Rooted_ROM
1. Place the ROM zip in the root of your ext sdcard.
2. Make certain that you have the latest Safestrap v3.72(NB1)apk (Download and learn more about SS from this thread:http://forum.xda-developers.com/showthread.php?t=2448925).
3. Boot into Safestrap recovery, perform an advanced wipe and wipe everything except ext sdcard.
4. Flash the ROM zip in Stock Slot.
5. Press "Home," then reboot into Download Mode and flash the I337_NC1_Stock_Kernel in PDA slot in Odin(AP in Odin v3.09+).
Once complete the phone will reboot and pause on the white AT&T splash screen for about 1-2 minutes before completely booting into the ROM. Done!
- It's recommended that you use Safestrap's Backup function to backup user data prior to flashing the ROM. Make sure and thank @loganfarrell for discovering this useful feature.
- In general, to flash a different 4.4.2 SS Custom ROM after flashing this ROM reboot into SS recovery, perform an advanced wipe, and wipe everything but ext sdcard. Then flash the new ROM in Stock Slot and reboot (refer to the other ROM's dedicated thread for any additional requirements or for assistance).
Known Issue: Safestrap.apk will force close after updating to NC1 using this method, however safestrap recovery will continue to function. To manually uninstall safestrap use es file explorer to delete system/etc/safestrap and system/bin/e2fsck then rename system/bin/e2fsck.bin to e2fsck (save these files if you wish to manually reinstall SS at a later time).
I337UCUFNC1_100%_Stock_Rooted_TetherAddOn
Instructions:
1. After flashing and booting into I337UCUFNC1_100%_Stock_Rooted_ROM or I337_NB1toNC1_KeepRoot_OTA.zip,
2. Place the AddOn in ext sdcard.
3. Reboot into Safestrap recovery and flash the AddOn in Stock Slot (Do Not Wipe Prior to Flashing)
4. Reboot. Done!
Click to expand...
Click to collapse
I have an I337UCUFNC1 Stock Unrooted
In your OP #3 Boot into Safestrap recovery.
How do you install Safestrap v3.72 when ROOT Requirement is needed?
I tried to install Safestrap Zip from recovery and it Failed and wipe my phone.
How do I root phone. Tried Saferoot, Kingo with no luck.
Can I do the I337_NB1toMK2_Downgrade to get root with my I337UCUFNC1 Stock?
Has anyone figured out how to restore recovery if it is lost after update to NC1? Pulling out what little hair I have left....
ClubWDW said:
Has anyone figured out how to restore recovery if it is lost after update to NC1? Pulling out what little hair I have left....
Click to expand...
Click to collapse
I'm having the issue. Apk won't function properly and I don't have the folder in etc directory.
Thanks.
EASY... relatively speaking.
I read XDA forums for hours and hours... and hours. Seriously. I spent about 20 hours reading XDA just for this. All the info is out there, but it is spread out across a dozen different threads, and multiple posts within those threads.
When I actually went through the process, I had (no lie) eighteen windows open, each with a relevant thread/post.
Sheesh, and people think this is complicated... [/s]
But in the end - I have a custom Lollipop ROM on my phone (Goldeneye v53) and it is working beautifully. And I had NO issues with the process, it all went smoothly.
The phone (which previously was starting to run out of space, lag, and just all-around felt "old") is now like new. And, dare I say... better than a stock S6? It is certainly leaner and meaner than a stock system (that's a good thing - I despise all the bloat on stock systems)
So, to make it easier for all those who come behind me, here is how to do it. In 39 easy steps.
One post.
One list.
Bullet points.
Links.
EASY.
Do this EXACTLY - and you will have a custom ROM on your S4.
Do something "just a little" different... Or miss a step... I'm pretty sure your device will explode, or at least catch on fire.
Either way, there is no express or implied warranty on this process I have collected and posted here. Anything you choose to do to your device is on you, and if something goes wrong, I accept no liability.
For risk mitigation in my case (as I'm an overly anal type) - I made sure that I dug my previous phone out of the closet, charged the battery, installed my SIM, and confirmed that I could use the old phone to at least make calls/texts in the event that "something" happened to my S4 during the upgrade process and I had to go to work the next day without my S4. Everything went smoothly, but IMO you should definitely have a contingency plan just in case.
Note - this is only for those NOT on MDB or MDL bootloaders. You guys have it easy. Don't do all the crap below - you don't need to, and if you DO do it, you are locked into this "complicated" method FOREVER (mwa-ha-haaa!!!)
1. Preparation
1.1 READ THROUGH THIS POST 27 TIMES (NO LESS, NO MORE) AND MAKE SURE YOU "GET IT". IF NECESSARY, READ THE THREADS LINKED THROUGHOUT THIS POST. <<< THIS IS THE SINGLE MOST IMPORTANT PART OF THE PROCESS. IF YOU JUST READ THE FIRST FEW STEPS AND START FLASHING CRAP, YOU ARE GOING TO F SOMETHING UP. READ IT ALL, UNDERSTAND IT, THEN DO IT. I CAN'T EMPHASIZE THIS ENOUGH.
1.2 Backup. Back your stuff up. Back it all up - ALL of it. Understand that whatever you do not back up now, YOU WILL LOSE. This process is going to wipe your device clean. Anything you want to save, you need to back it up now.
1.2.1 Do not use Titanium Backup - for anything. It will F your stuff up. Which is unfortunate, because TB is a great app that is incredibly useful - just not this time. Apparently TB has issues when migrating form one version of Android to another (i.e. 4.x.x to 5.x.x). Sorry, but you gotta do it manually.
1.2.2 Copy your pics/vids to your PC
1.2.3 Use "SMS Backup& Restore" from the Play store
1.2.4 Let Google sync your contacts and calendar.
1.2.5 Any apps that store your data locally (not sync'd to their server) - manually find it (I like ES File Explorer) and copy it to your PC if you care about it.
All of that said - I found that wiping my device and migrating to Lollipop was a GREAT way to clean a bunch of useless crap I no longer needed off of my phone.
2. Rooting and Flashing STOCK KitKat (4.4.2) ROM (relevant thread - see post #2, under the "NB1 - KitKat 4.4.2 > Option 2" section.
Note: The reason you have to do this is because you must have rooted Lollipop on your device in order to flash custom Lollipop ROMS. If you just want stock, non-rooted Lollipop maybe you COULD just use Odin to flash Lollipop directly? But there is no way to get root on Lollipop directly - and you must be rooted if you want to wind up with a custom ROM. So you have to do this intermediate step of flashing and rooting a 4.4.x or higher OS. This version of NB1 is easiest because you can use Odin to flash a ROOTABLE ROM which makes the root process simple with Towelroot.
2.1 Download Odin v3.09 here. Place on PC.
2.2 Download ROOTABLE NB1 ROM here. Place on PC.
2.3 Download towelroot v3 here. Place on PC and copy to device (likely your SD card).
2.4 Use Odin to flash ROOTABLE NB1 ROM to your device. When the phone boots up, just speed through the "initial setup" screens, it doesn't matter since you're going to install a couple more ROMs before the finished product.
2.5 Go to settings>more>security and check "unknown apps", and uncheck "verify sources".
2.5 Navigate to towelroot v3, and install it.
2.6 Open towelroot and click the "make it rain" button.
Congrats, you are now rooted on KitKat NB1.
3. Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method (relevant thread)
As mentioned, this process takes you from ROOTED NB1 (KitKat, 4.4.x) to OC3 (Lollipop, 5.x.x). The only way to get rooted OC3 is to first get root in any 4.4.x version or higher and then upgrade to OC3 using the "keep root" method. There is (as of this writing) no way to root OC3 Lollipop directly. "keep root" reference thread - post #1
3.1 Download Flashfire app using below steps. (no direct link available).
3.1.1 Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
3.1.2 Sign up to receive the BETA versions from Play Here.
3.1.3 Use the link provided after sign-up to download the app. Note - the link was not immediately available for me, and apparently that is normal. (There was a link, but it told me something like "link not found" when I tried to access it at first.) I had to sign up, and then 30 minutes later I went back and had access to the Flashfire file.
3.2 Download I337_OC3_Stock_Rooted_ROM here.
3.3 Place ROM on SD card.
3.4 Use Flashfire to flash ROM (see "keep root" reference thread from above for specific details of using Flashfire)
Congrats, you are now on rooted (stock) Lollipop.
4. Install your CUSTOM Lollipop ROM
4.1 Download ROM and prepare Safestrap recovery
4.1.1 Download your chosen ROM. I chose Goldeneye v53 here. (I chose Goldeneye because after brief reading, Goldeneye seemed to be one of the more stable options, and stability is what I wanted when going through this the first time.) Place it on your SD card. Here are other options for Lollipop custom ROMs on AT&T GS4. If you happen to wander into the development section and see all the shiny, new, intriguing ROMs floating around, keep in mind that most of them won't work for the AT&T GS4. Any custom ROM on this device must be based on Touchwiz and setup to be compatible with safestrap - only a handful meet those criteria.
4.1.2 Download Safestrap v3.75 here. Place it on your SD card. Do not install it at this point, Safestrap is currently not compatible with Lollipop - you are going to flash a different Kernel in Step 4.2 to work around this.
4.1.3 Download BusyBox from Play store
4.1.4 Install BusyBox on your device.
4.1.5 Install Safestap 3.75
4.1.6 Open Safestrap
4.1.7 I did not do this step because I did not start this process with any previous version of SS on my phone. But if you did have a previous SS recovery installed, use the Safestrap to "uninstall" the previous recovery version. It is my understanding that you can't install v3.75 on top of another version, you need to first remove the old version before installing the new version. The "uninstall" option is done from within the SS app, not the Android application manager - you are uninstalling the custom recovery, not the SS app.
4.1.8 "Install Recovery" (from within Safestrap). NOTE: this only INSTALLS safestrap, it does not boot you into safestrap recovery. There is no need to go into safestrap recovery yet. That's later.
4.2 Flash NC1 Kernel
As mentioned above, you need to flash the NC1 Kernel so that you can do your thing in Safestrap. But then you MUST remember to reflash the OC3 Kernel after using Safestrap to install the ROM, or else your phone will explode (probably).
4.2.1 Download NC1 flasher app from here. Place it on your SD card.
4.2.2 Download I337_stock_OC3_kernel_recovery_flashable from here. Place it on your SD card.
4.2.3 Download OC3 modules from here. Place it on your SD card.
4.2.4 Open NC1 flasher app and press "flash" (it's the only button)
4.2.5 Wait for completion and press reboot. NOW you will get automatically rebooted into safestrap recovery.
4.3 Install your custom ROM!!!
(note: all the below is done in safestrap recovery)
4.3.1 Go to "Wipe" and perform factory reset (will wipe system data, cache, and dalvik)
4.3.2 Flash your ROM. For Goldeneye ROM, it uses the AROMA installer. Choose the options that you like, but make sure to READ THEM ALL BEFORE SELECTING ANYTHING - IF ONE OF THE OPTIONS MENTIONS AT&T/SAFESTRAP, YOU MUST CHOOSE THAT OPTION. HELLFIRE, BRIMSTONE, AND ETERNAL DAMNATION WILL AWAIT YOU IF YOU CHOOSE ANOTHER OPTION.
4.3.3 At the end of the ROM installation, uncheck the "reboot now" option and continue - it will send you back to safestrap.
4.3.4 From within SS, install the OC3 modules from your SD card.
4.3.5 From within SS, install the I337_Stock_OC3_kernel_recovery_flashable from your SD card.
4.3.6 Reboot > system
4.3.7 Keep hitting "continue" when you get the safestrap recovery screen. This is a symptom of Lollipop not being compatible with Safestrap. Hit "continue" repeatedly (like 4 or 5 times) and eventually you will get into your ROM.
4.3.8 (Optional) Install safestrap.apk (that you d/l to your SD card) to your phone, and then use it to UNINSTALL recovery. This will avoid the above step 4.3.7 happening every time you reboot your phone.
Congrats, you now have a custom Lollipop ROM running on your device.
Note: SuperSU is finicky on Lollipop. See this thread for how to manipulate SuperSU to get your root apps working.
.
.
.
.
See? EASY.
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Israelsalinas19 said:
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Click to expand...
Click to collapse
You probably missed the step where he said to flash the nc1 kernel.
Yup, safestrap is known to be not fully compatible with OC3, that's why you have to flash the NC1 kernel in order to be able to use SS to flash your custom ROM. Don't forget to flash back to the OC3 kernel though, as stated in step 4.3.4.
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
robot_head said:
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
So you got all the way to step 4.3.6 successfully, it sounds like? And now you are just getting the Safestrap screen - where you can either "continue" or "recovery"? How many times did you hit "continue" and go through the "bootloop" (if any)?
After step 4.3.6, when you boot into your custom ROM, you will have the Safestrap screen pop up several times (like, at least four or five) - keep hitting "continue" and you will eventually get into the ROM. This is another symptom of Lollipop not being fully compatible with Safestrap.
I did not put that detail in the writeup. Very sorry it caused you issues. I am updating with that info now.
I must of not been patient enough, with so many failed rom installs with this locked bootloader i just odin'd back to nb1 to get to oc3... Any custom recovery would be such a relief as ss acts wonkey in lollipop, and flashfire isn't accessible if you're caught in a bootloop or the radical "att unauthorized software". Thanks for the help
Sent from my sghi337 on oc3
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
robot_head said:
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
Did you try wiping data/cache in the stock system recovery?
Yes wiped with system recovery and safestrap. This is an issue of flashing the oc3 kernels and modules with safestrap. I think.....
sent from my sghi337 on oc3
Read through your tutorial, very nice. ?The only thing I noticed is you flash the kernel before the modules. I think flashing the kernel should be the very last step before rebooting, I'm not sure it matters, but it might. Also when the phone is booting I never touch any buttons (continue or recovery) just let it work through the screens on it's own.
Thanks, Cats_PJs - I will edit the OP to indicate flashing the modules before the kernel. I didn't see such a recommendation to flash one or the other first in my research, and I honestly can't remember now which I flashed first. But I will update the OP to recommend flashing the kernel last, just in case.
If I'm safestrap'd and rooted on a custom 4.x.x ROM, should I flash to rootable NB1 per step 2.2 then start here with step 3? Thanks for compiling all this, I chuckled at the 18 pages open comment. I know that pain.
What version are you running now? If you already have root on a KitKat 4.4.x or higher ROM, you should be able to go straight to rooted Lollipop using the muniz_ri keep root method method here. (see the very first line of the linked reference post.) So if you meet that criteria, you could start in Step 3.
If you're on a lower build, you'll want to just start with step 2 and flash NB1 via Odin. I believe that you will need to uninstall your current version of safestrap at some point to be able to install the required v3.75.
So I have an update I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading. I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels you still have to safestrap your ROM though. In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required you must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin. So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must downgrade your kernel (via odin or nc1 flasher) then you can use safestrap to flash your ROM and flash your oc3 modules then reboot into download mode and use Odin to flash your oc3 kernel(sometimes it will fail,just try again, i hold my phone gently to comfort it through the process) and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Sent from my GT-I9505 using XDA Free mobile app
robot_head said:
So I have an update
I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading.
I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels - you still have to safestrap your ROM though.
In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required
You must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin.
So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must:
downgrade your kernel (via odin or nc1 flasher)
then you can use safestrap to flash your ROM and flash your oc3 modules
then reboot into download mode and use Odin to flash your oc3 kernel (sometimes it will fail, just try again, i hold my phone gently to comfort it through the process)
and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Click to expand...
Click to collapse
robot_head, glad to hear you got the custom ROMs working on your device! I will add a note in the OP regarding your experience so it helps others that might have the same issue.
Sorry, but stupid question - you did only try to install flashable ".zip" files from within safestrap, and ".tar" files using Odin? Your word choice in your above post seems to indicate that you do recognize the difference. But I ask that because I did not realize the difference at one point, until I tried to load a .zip into Odin and encountered issues. (and also I wanted to make this distinction for any others reading this thread)
Question for you – when you are swapping between custom ROMs, are you backing up your system settings and apps/data, then restoring them to each ROM (or are you just “sampling” each ROM for limited time and not worrying about your apps)? Based on advice I read in several places, I didn’t use Titanium Backup when I upgraded from 4.x.x to 5.0.1, but I figured I could use it to swap between ROMs now that I’m on Lollipop. But I just wanted to be sure I could easily move between ROMs without requiring so much time manually downloading apps like I did for the upgrade.
@sac02 yes I do have backups of all of my firmware and roms and yes I am just sampling through all of the roms and any apps that I need backed up are on my SD card and Google Play backs up the ones from them automatically. Yes when I'm flashing with safestrap obviously it has to be a zip file and Odin has to be a tar. And if you search the site there are downloads for your kernel in a tar format I actually got half of the help I needed from this thread and the other half from the Goldeneye thread when someone was having an issue with safestrap they had to Odin everything.
Sent from my GT-I9505 using XDA Free mobile app
The instructions are good. You may have a bad download of kernel file. Note that the instructions call for the "reflashable kernel zip file" which can also be found on the NC1 flasher thread.
My main problem is i couldnt flash kernels with safestrap after the rom. Tried a different download, same thing. Either said unauthorized att software
Or firmware update failed, use kies
Or bootloop into system recovery.
Finally. ..just odining kernels solved my issue.
Sent from my GT-I9505 using XDA Free mobile app
I have root on a base NJ4 4.4.4 ROM. I couldn't get the google play edition working on my i337 (dimming sensor worked poorly during calls) so I went to something basic. I'll try your recommendation, thanks again.