Related
Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)
shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...
Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone
Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP
Already answered
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?
but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb
Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app
Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?
No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app
Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:
New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)
I tried to do some searching but couldn't really find what I wanted, so I'm hoping someone can help answer my questions.
1) Is there any point on staying with MF3? Is it recommended I upgrade to another version, as long as SS works with it?
2) What version should I upgrade to? So far, I haven't cared about Roms on my S4, but I like the idea that I can always flash a rom, if wanted.
3) What is the recommended path to upgrading so that I can keep all my data? I saw through some posts that upgrading through update.zip would help secure my data. Are there any concerns with that method?
4) Just expanding on the first question, but will I lose anything from upgrading other than the ability to downgrade or install older roms, or even Google Edition Roms?
What I currently have (that may of concern)
A) Safestrap installed (but only my default rom slot) - So nothing really done with SafeStrap. I did make a Nandroid Backup.
B) Xposed installed with several Xposed Modules (Wanam Xposed being one of them).
C) I have made changes to the Theme colors (mainly notifcation bar) and tweaked some of the Notification bar icons through the Wanam Xposed Module.
Thanks for your help!
If I were on mf3. I'd upgrade to mk2 , root, and then install safestrap
Sent from my Nexus 5 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2616221
Sent from my SGH-I337 running GPE using Tapatalk
jd1639 said:
If I were on mf3. I'd upgrade to mk2 , root, and then install safestrap
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply. So can you confirm these are the proper steps to upgrade and not lose any data?
1) Un-install Safestrap.
2) Un-install Xposed Modules (is this necessary?)
3) Download and sideload mk2 update.zip from here: http://forum.xda-developers.com/showthread.php?t=2573080
4) Boot in stock recovery and install update.zip
** Phone should now be updated to mk2.
5) See if Root SurvivalMode worked, if not root with Saferoot from here: http://forum.xda-developers.com/showthread.php?t=2565758
6) Re-install safestrap
7) Enjoy updated GS4.
I assume having Safestrap installed and Xposed Modules has not affected any of my system files? Because I read that flashing the Unadultered MF3 first may be necessary. Do you think that would apply to my case based on the information I provided?
ccsoccer23 said:
Thanks for the quick reply. So can you confirm these are the proper steps to upgrade and not lose any data?
1) Un-install Safestrap.
2) Un-install Xposed Modules (is this necessary?)
3) Download and sideload mk2 update.zip from here: http://forum.xda-developers.com/showthread.php?t=2573080
4) Boot in stock recovery and install update.zip
** Phone should now be updated to mk2.
5) See if Root SurvivalMode worked, if not root with Saferoot from here: http://forum.xda-developers.com/showthread.php?t=2565758
6) Re-install safestrap
7) Enjoy updated GS4.
I assume having Safestrap installed and Xposed Modules has not affected any of my system files? Because I read that flashing the Unadultered MF3 first may be necessary. Do you think that would apply to my case based on the information I provided?
Click to expand...
Click to collapse
If you flash the unadulterated MF3 then you only have to uninstall Safestrap. Otherwise you do need to remove the xposed framework through the installer.
Sent from my SGH-I337 running GPE
ccsoccer23 said:
Thanks for the quick reply. So can you confirm these are the proper steps to upgrade and not lose any data?
1) Un-install Safestrap.
2) Un-install Xposed Modules (is this necessary?)
3) Download and sideload mk2 update.zip from here: http://forum.xda-developers.com/showthread.php?t=2573080
4) Boot in stock recovery and install update.zip
** Phone should now be updated to mk2.
5) See if Root SurvivalMode worked, if not root with Saferoot from here: http://forum.xda-developers.com/showthread.php?t=2565758
6) Re-install safestrap
7) Enjoy updated GS4.
I assume having Safestrap installed and Xposed Modules has not affected any of my system files? Because I read that flashing the Unadultered MF3 first may be necessary. Do you think that would apply to my case based on the information I provided?
Click to expand...
Click to collapse
During the update, even files outside of /system are checked. For all the files checked, if it finds anything altered, the update will fail. You can try the update without reverting anything, it will do the validations first and fail if it finds anything modified. You can then start uninstalling stuff and retry.
Typically, its a hassle to undo everything to return back to stock (we might have forgotten all the changes that we did to the phone) and that's why it is recommended to flash stock firmware directly. You would lose data in that case.
If you think you need to flash stock, you can directly flash MK2.
jmjoyas said:
During the update, even files outside of /system are checked. For all the files checked, if it finds anything altered, the update will fail. You can try the update without reverting anything, it will do the validations first and fail if it finds anything modified. You can then start uninstalling stuff and retry.
Typically, its a hassle to undo everything to return back to stock (we might have forgotten all the changes that we did to the phone) and that's why it is recommended to flash stock firmware directly. You would lose data in that case.
If you think you need to flash stock, you can directly flash MK2.
Click to expand...
Click to collapse
Updating this thread to say that the following steps did not result in me being on MK2:
3) Download and sideload mk2 update.zip from here: http://forum.xda-developers.com/show....php?t=2573080
4) Boot in stock recovery and install update.zip
** Phone should now be updated to mk2.
It ended up keeping me on MF3 and resetting my Phone.. That was no fun. I ended up using ODIN and the MK2 Odin files to flash to MK2. Now I'm on MK2, but lost a lot of my stuff saved on my phone. I guess I didn't backup enough. Lesson learned.
I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.
You need to set selinux to permissive mode and then you should be able to install safestrap recovery. Use selinuxmodechanger app for that
what's up with this software? anyone got 3.72b working on NB1?
burgertime78 said:
I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.
Click to expand...
Click to collapse
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.
Wanabedev83 said:
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.
Click to expand...
Click to collapse
That worked like a charm - the SELinux change app.
Thanks JmJoyas!
burgertime78 said:
That worked like a charm - the SELinux change app.
Thanks JmJoyas!
Click to expand...
Click to collapse
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.
Wanabedev83 said:
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.
Click to expand...
Click to collapse
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.
burgertime78 said:
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.
Click to expand...
Click to collapse
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.
Wanabedev83 said:
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.
Click to expand...
Click to collapse
Not sure of a thread for that. However, last night I installed over top of my stock slot. Apparently, KitKat does not allow flashing to "rom slot 1-4" so, I just did a full backup in safe strap, then wiped the stock slot and installed over top of it. worked fine.
Ok, after my last attempt to follow the instructions and spending over a full day with a bricked phone, I don't trust myself to do it again.
But I refuse to let the bloatware have its way...
So if someone can work me through the process to installing an easy, basic ROM I would highly appreciate it.
My phone is a Samsung Galaxy s4. i337. AT&T service, and it's on stock right now. 4.4.2. That's all I can tell you, I think it's Mk2 but I'd like to be able to find a way to MAKE SURE, before I screw anything up.
I have Odin, and I'm about to root my phone. If anyone will help me I'd greatly appreciate it!
i don't think you need odin anymore since towel root. i'm fairly certain it is just root, install safestrap, flash rom, flash root and carrier modules enjoy. goldeneye is a really nice rom for these phones with all the bloat removed and a few nice tweaks and addons.
exactly what i did last time, i flashed the new goldeneye with safestrap and it was brick city for 24 hours...
everything went fine and then it went into a bootloop when it tried to restart
First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?
Damani311 said:
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?
Click to expand...
Click to collapse
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nb1
sweet
recommendations?
Damani311 said:
nb1
sweet
recommendations?
Click to expand...
Click to collapse
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM to the stock slot (our version of Safestrap only supports the stock slot). When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.
Frankenscript said:
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM. When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.
Click to expand...
Click to collapse
wow awesome dude thanks a ton!
got to the part after installing safestrap, where it's time for goldeneye
which version of the rom should i use? the newest one got me in big trouble last time?
and so I'm going to need 4 zip files on my phone before i flash ROM?
Flash Goldeneye
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip
?
If so i'll proceed.....thanks again
I'm using Golden Eye v36. However, I've seen folks saying v38 (current) is good too... not sure where the problem cropped up with your last attempt so I can't speculate what the problem was.
And you're right, there should be 4 zip files on your SD card. The ROM, SuperSU, NC1 module, and the ATT APN/BuildProp file, which may not be necessary but worked fine for me.
alright looks like I'm up and running! wifi doesnt work, I think that's the only issue I can detect so far.........
WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Frankenscript said:
WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
i was hoping that was it, but it didn't get it....shoot
thanks for helping me out here
i flashed the jfleatt nb1 modules, btw
I'm out of ideas, sorry! Maybe start a thread about module not restoring WiFi after flash. My one relevant data point is that once, instead of Odin NB1 then flash NC1 update, I odined the rootable NB1. After that I did safestrap and flashed a ROM plus modules. I was never able to get WiFi no matter what I flashed. Odined back to regular NB1 then did NC1 update. Flashed ROM and modules again... Success. I assume kernel (locked on nc1 for me) has to interact with ROM and module. Improper match causes fail. Are you certain of what baseband you have?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Did you do the Selinux thingy--:good:
rugmankc said:
Did you do the Selinux thingy--:good:
Click to expand...
Click to collapse
Damani311,
Were you able to sort out the WiFi? Poking around the internet it does seem like permission issues are often at root of it, and the Selinux Mode Changer mentioned above (set to permissive) might be the solution.
Good luck! :good:
I think he is sorted based on posts on other threads. Maybe he will let us know--:good:
In just a couple of words, here's a basic overview of the ROM-flashing process:
- Root using Towelroot
- Install SuperSU
- Install Safestrap
- Download ROM
- Download modules
- Flash both
- Reboot
- Enjoy
Just make sure that whatever firmware you're on matches the ROM and modules (ex. NB1 users flash NB1 ROMs or MK2 ROMs and NB1 modules)
Best of luck! :good::good::good:
Appreciate your reply, but think OP is sorted and never came back--
I'm currently on 4.2.2 and I'm trying to figure out the quickest way to 5.0, or whatever is the most recent, to be able to get back up to speed. I'm also wanting to finally unlock my phone and get TWRP too after I get my phone updated to the most recent version. Thanks for any help!
4.4.2 not 4.2.2
Sent from my SM-N900V using XDA-Developers mobile app
Go back to factory 4.4.2 no root. Take new update to 5.0 OF1 from Verizon then root phone install Super SU make shure you have root. Then unlock bootloader install TWRP and you're ready to flash. Everything you'll need is in the General Forum
Sent from my SM-N900V using XDA Free mobile app
buckeyestilidie said:
4.4.2 not 4.2.2
Click to expand...
Click to collapse
Yeah I was sort of wondering about that - i think that would predate even MI9.
Is your phone already rooted, or not? The 'samsung_unlock_n3' thing can provide you with immediate access to a custom recovery (twrp-3.0.2-0-hltevzw-4.{x}.img with {x} = 3 or 4). Perform the retail-to-DevEd conversion with 'samsung_unlock_n3', and after you verified that it worked, just 'dd' the recovery image into the recovery partition with a root shell. No Odin, no incrementing your bootloaders, no re-rooting a stock device.
Then boot into the TWRP recovery with a 3-finger salute (Vol-Up+Home+Pwr), blow the Knox Warranty fuse by booting TWRP, take a TWRP backup, get it off onto some safe media, and you are ready to start doing what you want. Try the -4.3 image if the -4.4 wont boot.
Note: hltevzw, *not* hlte
bftb0 said:
Yeah I was sort of wondering about that - i think that would predate even MI9.
Is your phone already rooted, or not? The 'samsung_unlock_n3' thing can provide you with immediate access to a custom recovery (twrp-3.0.2-0-hltevzw-4.{x}.img with {x} = 3 or 4). Perform the retail-to-DevEd conversion with 'samsung_unlock_n3', and after you verified that it worked, just 'dd' the recovery image into the recovery partition with a root shell. No Odin, no incrementing your bootloaders, no re-rooting a stock device.
Then boot into the TWRP recovery with a 3-finger salute (Vol-Up+Home+Pwr), blow the Knox Warranty fuse by booting TWRP, take a TWRP backup, get it off onto some safe media, and you are ready to start doing what you want. Try the -4.3 image if the -4.4 wont boot.
Note: hltevzw, *not* hlte
Click to expand...
Click to collapse
Okay that was a lot of information I'm not too sure about lol yes I am rooted and I'm pretty sure I'm using safestrap as my recovery.
Sent from my SM-N900V using XDA-Developers mobile app
bftb0 said:
Yeah I was sort of wondering about that - i think that would predate even MI9.
Is your phone already rooted, or not? The 'samsung_unlock_n3' thing can provide you with immediate access to a custom recovery (twrp-3.0.2-0-hltevzw-4.{x}.img with {x} = 3 or 4). Perform the retail-to-DevEd conversion with 'samsung_unlock_n3', and after you verified that it worked, just 'dd' the recovery image into the recovery partition with a root shell. No Odin, no incrementing your bootloaders, no re-rooting a stock device.
Then boot into the TWRP recovery with a 3-finger salute (Vol-Up+Home+Pwr), blow the Knox Warranty fuse by booting TWRP, take a TWRP backup, get it off onto some safe media, and you are ready to start doing what you want. Try the -4.3 image if the -4.4 wont boot.
Note: hltevzw, *not* hlte
Click to expand...
Click to collapse
This seems like an easier way then mentioned above, but I'm vague on the terminology used. Could you elaborate on the ideas you explained?
Sent from my SM-N900V using XDA-Developers mobile app
buckeyestilidie said:
This seems like an easier way then mentioned above, but I'm vague on the terminology used. Could you elaborate on the ideas you explained?
Click to expand...
Click to collapse
I started writing a SBS (step by step), but as I took the time to make sure that nobody would shoot themselves in the foot with my instructions, I realized that it would take a huge amount of effort once all the caveats and "be careful here"s are included.
The only reason that I took the path I did is that I don't care much for dodgy/opaque rooting methods, so I just preferred to try a route that avoided losing root, even temporarily.
It basically boils down to writing the recovery image (e..g twrp-3.0.2-0-hltevzw-4.3.img or twrp-3.0.2-0-hltevzw-4.4.img) directly to the recovery partition (/dev/block/mmcblk0p15) from the rooted ROM using the "dd" program after you have unlocked the bootloader. You can find those recovery images here, and raw-writing looks like this (note root prompt '#' symbol) :
Code:
# dd if=twrp-3.0.2-0-hltevzw-4.4.img bs=2048 of=/dev/block/mmcblk0p15
***
(You need root for both this operation and to unlock the bootloader, so it makes most sense to unlock the bootloader first).
Note that the above says nothing at all about how to prepare for disasters before you travel down this path. All of that is your responsibility; if reading this makes you uncomfortable, then you shouldn't be doing it.
Among the things that I prepared beforehand: TiBu backups; full tar image of the "internal" /sdcard; full backup of external SDcard; Safestrap TWRP backups of all slots; raw dumps of all of the partitions p1-p22; debrick images (first 256 MB of /dev/block/mmcblk0) both before and after the CID-changing unlock method, another p6 (= aboot) partition raw copy *after* the unlock CID change, etc.
After I had a real recovery running on the phone, the first thing I did was to take TWRP backups of everything and got those backups off the phone as well.
Even after that, I think I forgot something: I think safestrap backs up the "loopback mount blobs" for the non-stock slots somewhere in /data/media - so they are not captured by backups of "real" TWRP (in the real recovery partition), nor in backups of the "internal" SDcard. They are captured by the psuedo-recovery that Safestrap uses, but the ability to use them may depend on having the stock slot be the active slot before you take the (real) TWRP backup. You will see similar instructions elsewhere: e.g. "get your rooted ROM running in the stock slot before you begin, and make sure the stock slot is the active slot"
*** The partitioning numbering scheme is not guaranteed to be identical on devices other than the SM-N900V Verizon Samsung Galaxy Note 3. If you have in mind using a command like this on another device, a better means for naming the destination (output file of=) target is "by-name", e.g.
dd ... of=/dev/block/platform/msm_sdcc.1/by-name/recovery ...
I didn't use that notation here because Safestrap plays games trying to protect the real boot partition by altering these symlinks, so you need to verify they really point where you think they do before you use them. (e.g. iirc, safestrap symlinks boot -> /dev/null and userdata -> mmcblk0p25 -> mount point of data blob for active slot)